[SERVER-23010] Committed Snapshot Meaning Incorrect Created: 08/Mar/16  Updated: 27/Mar/20  Resolved: 27/Mar/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.4

Type: Bug Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-23956 Inconsistent behavior between 3.2.6-r... Closed
is depended on by SERVER-22533 Enable ReadConcern.Majority tests wit... Closed
Duplicate
is duplicated by SERVER-22572 readConcern majority doesn't consider... Closed
Related
is related to SERVER-23365 Resolve ReadConcern passthrough failures Closed
is related to DOCS-7138 Describe new journal behavior in repl... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.2
Sprint: Repl 11 (03/11/16), Repl 12 (04/01/16)
Participants:
Linked BF Score: 0

 Description   

Currently with the changes for the SERVER-22276 (and SERVER-22495) the committed snapshot is not correctly being updated based on the replica set config and journal write concern flag.

Rules to apply to correct the problem:

The meaning of the snapshot depends on the replica set config (“writeConcernMajorityJournalDefault”) which indicates if it is tied to the durable or applied optime.

Notable Exceptions (when both aren't true or false)

  1. Applied Snapshot OpTime, with J:True
    • Wait for snapshot for writeOpTime (Applied)
    • Wait for replication of durableOpTime >= writeOpTime (new code)
  2. Durable Snapshot OpTime, with J:False
    • Do not wait for snapshot, and you cannot read your own write
    • Wait for replication of majority optime (applied = normal)


 Comments   
Comment by Githook User [ 07/Nov/16 ]

Author:

{u'name': u'Scott Hernandez', u'email': u'scotthernandez@tart.local'}

Message: SERVER-23010: general cleanup and test fixture changes

(cherry picked from commit 664295c8ca3152c48da572c770aa08c39e517bf4)
Branch: v3.2
https://github.com/mongodb/mongo/commit/605083d00f91c24595d3a112b7ab207d3cbb8aec

Comment by Githook User [ 01/Apr/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-23010: check if init'd before using snapshotInfo
Branch: master
https://github.com/mongodb/mongo/commit/07f98aaee975617b8778a4b296c1c3abdbaeb1c1

Comment by Githook User [ 28/Mar/16 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-23010: always wait for snapshot on WriteConcern.Majority
Branch: master
https://github.com/mongodb/mongo/commit/469dd5196c87a1ccb30f4ac1c7d46bd1ca6c113e

Comment by Githook User [ 27/Mar/16 ]

Author:

{u'name': u'Scott Hernandez', u'email': u'scotthernandez@tart.local'}

Message: SERVER-23010: do not update durable OpTime, and update commited snapshot, if not durable
Branch: master
https://github.com/mongodb/mongo/commit/ec1aaf5ce52bed2897e80cbba7add95c068809dc

Comment by Githook User [ 27/Mar/16 ]

Author:

{u'name': u'Scott Hernandez', u'email': u'scotthernandez@tart.local'}

Message: SERVER-23010: improved logging readconcern usage
Branch: master
https://github.com/mongodb/mongo/commit/7a5d4214ca939ff3e522a493d848f9f35ac88d5c

Comment by Githook User [ 27/Mar/16 ]

Author:

{u'name': u'Scott Hernandez', u'email': u'scotthernandez@tart.local'}

Message: SERVER-23010: change commmitted snapshot by either durable or applied optime
Branch: master
https://github.com/mongodb/mongo/commit/8e3849c3b7c4abe4ed27e4ca0ee3e01ea06e2384

Comment by Githook User [ 27/Mar/16 ]

Author:

{u'name': u'Scott Hernandez', u'email': u'scotthernandez@tart.local'}

Message: SERVER-23010: general cleanup and test fixture changes
Branch: master
https://github.com/mongodb/mongo/commit/664295c8ca3152c48da572c770aa08c39e517bf4

Generated at Thu Feb 08 04:02:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.