[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:
Depends
Related
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.
Instead, the read should block until such a snapshot is available.



 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: SERVER-19984 Block read committed reads after metadata changes, rather than returning an error
Branch: master
https://github.com/mongodb/mongo/commit/8f84d60e1615e798a18b99405844f7fb4bb96e50

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: SERVER-19984 remove read_majority_mmap.js from small_oplog_rs
Branch: master
https://github.com/mongodb/mongo/commit/27a72ae33245c9e5ff63006154ab64521c37be2c

Comment by Eric Milkie [ 17/Aug/15 ]

Indeed, we need to block instead of returning ReadMajorityNotAvailableYet in most cases.

Generated at Thu Feb 08 03:52:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.