[SERVER-27028] linearizable read concern does not check if node is still primary before it writes noop Created: 14/Nov/16 Updated: 19/Nov/16 Resolved: 15/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2016-11-21 |
| Participants: |
| Description |
|
If a stepdown occurs here, the noop write will still occur even though the node is now a secondary, leading to an inconsistent state: https://github.com/mongodb/mongo/blob/e82b201cf7d17f64f54b57f58dc9668527ab49b1/src/mongo/db/read_concern.cpp#L138-L142 |
| Comments |
| Comment by Githook User [ 15/Nov/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |