-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v7.3, v7.0, v6.0, v5.0
-
-
CAR Team 2024-01-22, CAR Team 2024-02-05
-
2
Currently spotted a bug where given 2 mongos:
- mongos1 : create a non-empty sharded collection
- mongos2: drop the collection and shards it as timeseries
in case mongos1 (which is now stale) runs createIndex it will fail 10 times without trying a refresh.
I attached a test to reproduce the error which is unclear.
The goal of the ticket is to investigate what is causing this issue.
Important notes:
- the issue does not happen if mongos1 creates an empty sharded collection (skip the insert)
- the issue does not happen if mongos2 creates a non-timeseries sharded collection
- the issue only happens because mongos1 does not refresh, but attempts again with the same version for 10 times
The ticket is necessary for track unsharded collection since after SERVER-81190 it will happen even if mongos1 just runs a insert.
Once the ticket is done, please fix the TODO
- is depended on by
-
SERVER-81190 Support tracking "simple" unsharded collections in the sharding catalog
- Closed
- related to
-
SERVER-69776 Increase test coverage for concurrent collection creation
- Closed