Essentially, the issue appears to be that listIndexes can read from the DurableCatalog in the middle of a concurrent collection rename (after the original target was dropped, but before the source collection is renamed). This looks to be possible because the listIndexes can read from the DurableCatalog using the same catalogId that the collection rename removes from the DurableCatalog.
Some ideas for how to fix this include making listIndexes no longer lock free as well as reimplementing listIndexes to use the IndexCatalog instead of the DurableCatalog.
- is depended on by
-
SERVER-52713 [testing] Add stepdown/kill/terminate to tenant_migration_jscore_passthrough
-
- Closed
-
- is duplicated by
-
SERVER-55519 Investigate missing _id index during collection cloning in tenant migration
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-