Skip to content

Connection between auto-retry, pinning, and request association #1760

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

Closed
wants to merge 1 commit into from
Closed

Connection between auto-retry, pinning, and request association #1760

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
8 changes: 4 additions & 4 deletions source/core/read-preference-mechanics.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,17 +101,17 @@ Auto-Retry
Connections between MongoDB drivers and :program:`mongod` instances in
a :term:`replica set` must balance two concerns:

#. The client should attempt to prefer current results, and any
connection should read from the same member of the replica set as
much as possible.
#. The client should attempt to prefer current results, and any connection
should read from the same member of the replica set as much as possible.
Requests should prefer :ref:`request association <replica-set-read-preference-behavior-requests>` (*pinning*).

#. The client should minimize the amount of time that the database is
inaccessible as the result of a connection issue, networking
problem, or :term:`failover` in a replica set.

As a result, MongoDB drivers and :program:`mongos`:

- Reuse a connection to specific :program:`mongod` for as long as
- Reuse a connection to a specific :program:`mongod` for as long as
possible after establishing a connection to that instance. This
connection is *pinned* to this :program:`mongod`.

Expand Down