-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04
-
154
Currently, RefineShardKey does not inform shards about the new collection version.
- causes
-
SERVER-80538 New refine collection shard key might resume migrations on unretriable errors
-
- Closed
-
-
SERVER-80715 New refine collection shard key might try to access invalid collection object
-
- Closed
-
-
SERVER-80890 _configsvrCommitRefineCollectionShardKey test should wait for the metadata to be fully replicated
-
- Closed
-
-
SERVER-93017 [test-only] Exclude configsvr_commit_refine_collection_shard_key.js from stepdown suites
-
- Closed
-
- depends on
-
SERVER-73130 getCollectionDescription doesn't honor the critical section
-
- Closed
-
-
SERVER-80246 Fsync test is not correctly checking for concurrent ddl operations
-
- Closed
-
- is related to
-
SERVER-97733 Re-enable filtering metadata check in tests that disabled it due to refineCollectionShardKey
-
- Open
-
-
SERVER-79064 Remove refine collection shard key deprecated code once 8.0 becomes last lts
-
- Closed
-