[SERVER-19234] Ensure that during idle periods, the latest write becomes visible to committed reads Created: 30/Jun/15  Updated: 02/Aug/18  Resolved: 20/Jul/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.1.6

Type: Task Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently there is a race condition if the snapshot for an optime is created after that optime is considered "committed". In that case, the snapshot will only be blessed the next time that the committed optime is bumped.

The plan is to move the list of snapshots out of ReplCoordinatorExternalState and into ReplCoordinatorImpl. This will allow us to consider a snapshot "committed" as soon as it is created if it's optime is before the commit point.



 Comments   
Comment by Githook User [ 07/Jul/15 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-19234 Move tracking of snapshots to ReplicationCoordinator from ExternalState

This allows blessing a snapshot as committed if it is created after its
OpTime has been marked as committed.

This commit also resolves SERVER-19208 (read committed on secondaries) by
unifying the code to advance the commit point on both primaries and
secondaries.
Branch: master
https://github.com/mongodb/mongo/commit/bbcf151c248fde365755a07d88af4fdc401cf5ac

Generated at Thu Feb 08 03:50:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.