From 4ba5c507b57c62f3ade79b536f6b411be2e81b24 Mon Sep 17 00:00:00 2001 From: Evan Cordell Date: Wed, 26 Apr 2023 11:53:29 -0400 Subject: [PATCH 1/2] update schema new enemy note --- content/annotations-intro.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/annotations-intro.yaml b/content/annotations-intro.yaml index 060d3f5..f965ed4 100644 --- a/content/annotations-intro.yaml +++ b/content/annotations-intro.yaml @@ -232,7 +232,8 @@ groups: namespace-new-enemy: content: | Here it looks like each `aclserver` is updating and caching versions of the namespace configuration individually by watching a change feed. - Interesting to note that this could theoretically lead to a "new-enemy problem" where older versions of a namespace are incorrectly interpreting tuples that were written at a later time. + Zanzibar avoids a schema-based "new-enemy problem", where older versions of a namespace are incorrectly interpreting tuples that were written at a later time, by globally tracking the highest timestamp at which all nodes have the namespace available. + See [§3.2.2](#3.2.2-config-consistency) voting-replica-write-latency-abroad: content: | From ea81040ec53d437a152178fbfd669388712e54d3 Mon Sep 17 00:00:00 2001 From: Evan Cordell Date: Wed, 26 Apr 2023 12:47:29 -0400 Subject: [PATCH 2/2] Update annotations-intro.yaml --- content/annotations-intro.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/annotations-intro.yaml b/content/annotations-intro.yaml index f965ed4..10a7f23 100644 --- a/content/annotations-intro.yaml +++ b/content/annotations-intro.yaml @@ -232,8 +232,8 @@ groups: namespace-new-enemy: content: | Here it looks like each `aclserver` is updating and caching versions of the namespace configuration individually by watching a change feed. - Zanzibar avoids a schema-based "new-enemy problem", where older versions of a namespace are incorrectly interpreting tuples that were written at a later time, by globally tracking the highest timestamp at which all nodes have the namespace available. - See [§3.2.2](#3.2.2-config-consistency) + Zanzibar avoids a namespace-based "new-enemy problem", where older versions of a namespace are incorrectly interpreting tuples that were written at a later time, by globally tracking the highest timestamp at which all nodes have the namespace version available. + See [§3.2.2](#3.2.2-config-consistency). voting-replica-write-latency-abroad: content: |