Operational Defect Database
BugZero found this defect 59 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2616235
Figure out how to handle NamespaceNotFound error in TTL Index Delete
Last update date:
3/21/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
As part of the new rs->configShard procedure, there is a period of time where users are connected directly to a replica set started with --configsvr, but the replica set has not been added as a shard yet. As a result of this, TTL index delete will fail with NamespaceNotFound because it will attempt to get sharding database metadata which is only created after the replica set has been added as a shard. A possible solution could be to attempt to refresh the sharding filtering metadata on namespace not found error similar to how StaleShardVersion errors are handled.
Top User Comments
Steps to Reproduce
