Kyle K's suggestions #2794
Kyle K's suggestions #2794
Conversation
| prior to the start of the read operation. Linearizable read | ||
| concern returns data that cannot be rolled back. You can specify | ||
| concern returns data that will never be rolled back. You can specify |
There was a problem hiding this comment.
Hey Eric --
just wanted to double check. Given that we now state that possibly, writes issued with "w: majority" write concern could roll back, is the above still true? Wasn't sure what the mechanics behind linearizable reads are.
There was a problem hiding this comment.
Where do we say w:majority write concern writes could roll back? I'll check everything for continuity.
There was a problem hiding this comment.
There was a problem hiding this comment.
Oh right. The Note applies to this blurb about linearizable reads as well.
There was a problem hiding this comment.
Could I then tweak to:
For replica sets that run with writeConcernMajorityJournalDefault set to true, linearizable read concern returns data that will never be rolled back.
With writeConcernMajorityJournalDefault set to false, MongoDB will not wait for w: "majority" writes to be durable before acknowledging the writes. As such, "majority" write operations could possibly roll back in the event of a loss of a replica set member.
|
merged! |
* DOCSP-28023 Sharding Note (#2752) * DOCSP-28023 Adds note to config server setup * Adds note to auth YAML * Fixes per Jeff * Fixes per Jeff * DOCSP-28854 Fixes build error (#2798)
This change is