From 6405bf77d5f437ee33a7145f8589b186c292818f Mon Sep 17 00:00:00 2001 From: Rich Loveland Date: Wed, 23 Sep 2020 11:37:37 -0400 Subject: [PATCH] Fix incorrect Follower Reads interval Fixes #8262. --- v20.1/topology-duplicate-indexes.md | 2 +- v20.2/topology-duplicate-indexes.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/v20.1/topology-duplicate-indexes.md b/v20.1/topology-duplicate-indexes.md index 21ee64f4833..cf9971a4c0d 100644 --- a/v20.1/topology-duplicate-indexes.md +++ b/v20.1/topology-duplicate-indexes.md @@ -179,7 +179,7 @@ Because this pattern balances the replicas for the table and its secondary index ## Alternatives -- If reads from a table can be historical (48 seconds or more in the past), consider the [Follower Reads](topology-follower-reads.html) pattern. +- If reads from a table can be historical (4.8 seconds or more in the past), consider the [Follower Reads](topology-follower-reads.html) pattern. - If rows in the table, and all latency-sensitive queries, can be tied to specific geographies, consider the [Geo-Partitioned Leaseholders](topology-geo-partitioned-leaseholders.html) pattern. Both patterns avoid extra secondary indexes, which increase data replication and, therefore, higher throughput and less storage. ## Tutorial diff --git a/v20.2/topology-duplicate-indexes.md b/v20.2/topology-duplicate-indexes.md index 679cd1f237c..2d32eca00d6 100644 --- a/v20.2/topology-duplicate-indexes.md +++ b/v20.2/topology-duplicate-indexes.md @@ -179,7 +179,7 @@ Because this pattern balances the replicas for the table and its secondary index ## Alternatives -- If reads from a table can be historical (48 seconds or more in the past), consider the [Follower Reads](topology-follower-reads.html) pattern. +- If reads from a table can be historical (4.8 seconds or more in the past), consider the [Follower Reads](topology-follower-reads.html) pattern. - If rows in the table, and all latency-sensitive queries, can be tied to specific geographies, consider the [Geo-Partitioned Leaseholders](topology-geo-partitioned-leaseholders.html) pattern. Both patterns avoid extra secondary indexes, which increase data replication and, therefore, higher throughput and less storage. ## Tutorial