[SERVER-19984] Block read committed reads after metadata changes, rather than returning an error Created: 17/Aug/15 Updated: 19/Sep/15 Resolved: 19/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.7 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Matt Dannenberg |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | RPL 8 08/31/15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
After making a metadata change, even if the writer waits for w:majority write concern, a subsequent read concern level majority read to a secondary node may return an error ReadMajorityNotAvailableYet, if that node has not yet produced and blessed a snapshot as the committed snapshot after the metadata change was applied. |
| Comments |
| Comment by Githook User [ 19/Aug/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Githook User [ 17/Aug/15 ] |
|
Author: {u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}Message: |
| Comment by Eric Milkie [ 17/Aug/15 ] |
|
Indeed, we need to block instead of returning ReadMajorityNotAvailableYet in most cases. |