[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: This allows blessing a snapshot as committed if it is created after its This commit also resolves |