[SERVER-33722] readConcern snapshot should return an error for metadata changes Created: 07/Mar/18  Updated: 29/Oct/23  Resolved: 14/Mar/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Eric Milkie Assignee: James Wahlin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-33698 batchSize:0 snapshot reads must alloc... Closed
Duplicate
is duplicated by SERVER-33664 add SnapshotUnavailable for atCluster... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-03-26, Storage NYC 2018-03-12
Participants:

 Description   

readConcern level majority will wait (block) when it detects it is about to acquire a Collection lock but the readConcern majority snapshot timestamp is less than the minimumVisibleSnapshot timestamp.
readConcern level snapshot cannot block in this situation because unlike readConcern majority, it cannot change its read timestamp. Therefore, it must return an error in this situation.

The error to return should be SnapshotUnavailable.



 Comments   
Comment by Githook User [ 14/Mar/18 ]

Author:

{'email': 'james@mongodb.com', 'name': 'James Wahlin', 'username': 'jameswahlin'}

Message: SERVER-33722 readConcern snapshot should return an error for metadata changes
Branch: master
https://github.com/mongodb/mongo/commit/8727cdfc81358fa829cb86153606b84efca4edfd

Generated at Thu Feb 08 04:34:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.