From 7265ccff6252d1f319a842518ebd53627255530b Mon Sep 17 00:00:00 2001 From: "A. Jesse Jiryu Davis" Date: Fri, 14 Dec 2012 15:04:16 -0500 Subject: [PATCH] Correct the description of RS monitoring for read prefs section: not everyone uses isMaster for this purpose --- source/applications/replication.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/applications/replication.txt b/source/applications/replication.txt index 5d59569ffe2..91c20b74a71 100644 --- a/source/applications/replication.txt +++ b/source/applications/replication.txt @@ -496,9 +496,9 @@ Member Selection ```````````````` Clients, by way of their drivers, and :program:`mongos` instances for -sharded clusters periodically call :dbcommand:`isMaster` on all members of the -replica set to update their view of the set's state, and to determine latency -from the application to each :program:`mongod` instance. +sharded clusters periodically update their view of the set's state: which +members are up or down, which is primary, and the latency to each +:program:`mongod` instance. For any operation that targets a member *other* than the :term:`primary`, the driver: