[SERVER-21028] read concern level majority checking is racy Created: 20/Oct/15 Updated: 27/Oct/15 Resolved: 23/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl B (10/30/15) | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
If setReadFromMajorityCommittedSnapshot() returns that there is no committed snapshot yet available, we then waitForNewSnapshot() and try again. |
| Comments |
| Comment by Githook User [ 23/Oct/15 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |
| Comment by Eric Milkie [ 20/Oct/15 ] |
|
The same race exists in _ensureMajorityCommittedSnapshotIsValid(), which contains the only other call of waitForNewSnapshot(). |