[SERVER-71278] Remove retry for SnapshotUnavailable error in global indexes code Created: 11/Nov/22  Updated: 29/Oct/23  Resolved: 19/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Allison Easton Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67289 Remove Feature Flag for PM-2218 Closed
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-05-29
Participants:

 Description   

Remove the sleep in the catalog cache added by SERVER-71168, designed to allow time for the config time to advance beyond the creation time of config.csrs.indexes.

Context:

During FCV upgrade when enabling theĀ 
gGlobalIndexesShardingCatalog feature flag, we are creating a new collection on the config server - config.csrs.indexes. The mongoS is also running an aggregation on this collection with snapshot read concern. Since the mongoS has no concept of FCV, it will start sending the aggregation to the config server as soon as the binary is changed to one with the feature flag enabled, regardless of the FCV of the config server. We have encountered the SnapshotUnavailable error after creating the collection and its indexes but before the journal flush happens.
Once this project finishes, presumably the aggregation will return NamespaceNotFound at the previous config time sent in the aggregation rather than SnapshotUnavailable, and the sleep to allow for journaling to complete can be removed.



 Comments   
Comment by Githook User [ 18/May/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-71278 Remove retry for SnapshotUnavailable error in global indexes code
Branch: master
https://github.com/mongodb/mongo/commit/4e246edc4364f389f36af9367b3109da7e4c8013

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