[SERVER-85986] establishConsistentCollections with timestamp not consistent Created: 30/Jan/24  Updated: 06/Feb/24

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Henrik Edin Assignee: Sulabh Mahajan
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Operating System: ALL
Sprint: CAR Team 2024-02-05, CAR Team 2024-02-19
Participants:
Story Points: 1

 Description   

establishConsistentCollections (that seems to establish consistent database) does not establish a consistent view of the database when a timestamp is provided. It uses the latest state of the collection catalog to determine which collections might exist and establishes a correct snapshot for them. However, collections that existed at the timestamp but has since been dropped would be missed.

We don't seem to use this with a timestamp so I suggest we remove the timestamp parameter to keep this simple.

If the desire is to establish a consistent database we'd need to traverse _nss in the historical catalogId tracker and filter on namespace and existence for a complete set of collections at the given time.


Generated at Thu Feb 08 06:59:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.