Operational Defect Database
BugZero found this defect 96 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2575579
Non-transactional snapshot read on unsharded collection may execute with mismatched sharding metadata
Last update date:
3/12/2024
Affected products:
MongoDB Server
Affected releases:
7.0.0
Fixed releases:
No fixed releases provided.
Description:
Info
SERVER-84723 omitted an anomaly that can occur on non-transactional snapshot reads on unsharded collections. Consider the following interleaving: Collection is sharded At T20 the collection is dropped At T30 the collection is recreated as unsharded (and not tracked by the sharding catalog) A client executes a find with readConcern=snapshot + atClusterTime=T10. In this case, the find will observe storage engine data as of T10, but the sharding metadata (and routing) will correspond to that of the present. So the find will miss documents.
Top User Comments
xgen-internal-githook commented on Fri, 1 Mar 2024 15:52:10 +0000: Author: {'name': 'Jordi Serra Torrens', 'email': 'jordist@users.noreply.github.com', 'username': 'jordist'} Message: SERVER-86583 Ensure non-transactional snapshot reads on unsharded collections operate with a correct sharding catalog (#18943) GitOrigin-RevId: 60ef48dc39200961af436609ab9110389d545a07 Branch: master https://github.com/mongodb/mongo/commit/6cb8661cb6ae13289483652bfcfce420801c6b6a
Steps to Reproduce
