Skip to content

Correct the description of RS monitoring for read prefs section: not everyone uses isMaster for this purpose #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 14, 2012
Merged

Correct the description of RS monitoring for read prefs section: not everyone uses isMaster for this purpose #477

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions source/applications/replication.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down