[SERVER-19208] Implement read committed on secondaries Created: 29/Jun/15  Updated: 02/Aug/18  Resolved: 07/Jul/15

Status: Closed
Project: Core Server
Component/s: None
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   

In the initial implementation they are not able to advance their commit point so they are never able to retire old snapshots.



 Comments   
Comment by Githook User [ 27/Aug/15 ]

Author:

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

Message: SERVER-19208 Add a basic test of majority readConcern on secondaries
Branch: master
https://github.com/mongodb/mongo/commit/40960734644db59ee630b26ac8398139440a63b5

Comment by Githook User [ 10/Jul/15 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-19208 some unittests for committed snapshots
Branch: master
https://github.com/mongodb/mongo/commit/27e0f7a4b5b407d43de33db941cd413ea46399cd

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:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.