From 76c3cab7348dec68e420ab255b8303bac6357ccf Mon Sep 17 00:00:00 2001 From: Venkateswara Reddy B Date: Fri, 3 Mar 2017 21:31:17 +0530 Subject: [PATCH] Corrected typo In case of maxStalenessSeconds mentioned as part read preference, the reads will be redirected to the secondary whose estimated lag less than the maxStalenessSeconds value and not greater than maxStalenessSeconds value. --- source/reference/read-preference.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/reference/read-preference.txt b/source/reference/read-preference.txt index 8f44cf2230a..ec3f93063c7 100644 --- a/source/reference/read-preference.txt +++ b/source/reference/read-preference.txt @@ -117,7 +117,7 @@ Read Preference Modes how stale each secondary is by comparing the secondary's last write to that of the primary, if available, or to the secondary with the most recent write if there is no primary. The client will then - filter out any secondary whose estimated lag is greater than + filter out any secondary whose estimated lag is less than ``maxStalenessSeconds`` and randomly direct the read to a remaining member (primary or secondary) whose network latency falls within the :ref:`acceptable latency window