[SERVER-23295] Uncommitted write visible with 'majority' readConcern after rollback Created: 22/Mar/16 Updated: 06/Apr/16 Resolved: 05/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Mathias Stearn | Assignee: | Eric Milkie |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Repl 13 (04/22/16) | ||||||||
| Participants: | |||||||||
| Description |
|
Following a rollback, a secondary appears to mark it's new state as committed even if the primary hasn't confirmed that the write has been accepted by a majority of votes. See the attached test file, especially the XXX comments. |
| Comments |
| Comment by Eric Milkie [ 05/Apr/16 ] |
|
Dup of |
| Comment by Scott Hernandez (Inactive) [ 25/Mar/16 ] |
|
The linked server issue ( After changing the test a bit, to do inserts only, since the bug will allow reading a newer state of the document retrieved during rollback, the test completes without error. I will cleanup the test and commit it to ensure there is no regression of this behavior. I will also continue to investigate once the linked issue is fixed to ensure there are no other issues before closing this with the test fix. |