Skip to content

[Lock] #37139 Updated Lock MongoDbStore note on readPreference #13775

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.

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
Changes from all commits
Commits
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
7 changes: 4 additions & 3 deletions components/lock.rst
Original file line number Diff line number Diff line change
Expand Up @@ -647,9 +647,10 @@ about `Expire Data from Collections by Setting TTL`_ in MongoDB.
locks don't expire prematurely; the lock TTL should be set with enough extra
time in ``expireAfterSeconds`` to account for any clock drift between nodes.

``writeConcern``, ``readConcern`` and ``readPreference`` are not specified by
MongoDbStore meaning the collection's settings will take effect. Read more
about `Replica Set Read and Write Semantics`_ in MongoDB.
``writeConcern`` and ``readConcern`` are not specified by MongoDbStore meaning
the collection's settings will take effect.
``readPreference`` is ``primary`` for all queries.
Read more about `Replica Set Read and Write Semantics`_ in MongoDB.

PdoStore
~~~~~~~~~~
Expand Down