-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA
-
Fully Compatible
-
Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, CAR Team 2023-11-13, CAR Team 2023-11-27
-
160
Currently, the shadCollection command is doing a best effort to inform involved shards about the new collection that they own. The goal of this ticket is to make shardCollection command shard authoritative, in order that, all shard will know about the filtering information that they own before serving any type of operation.
Documentation
- causes
-
SERVER-83552 Recreate create collection coordinator result with catalog cache refresh
- Closed
-
SERVER-83557 Create collection coordinator assume that getAllShardIds is sorted
- Closed
- depends on
-
SERVER-81353 Add a clean up procedure to the create collection coordinator
- Closed
-
SERVER-81370 Make all InitialSplitPolicy accept a set of available shards
- Closed
- duplicates
-
SERVER-77330 Extend scope of user write blocks while running shardCollection with hashed shard key
- Closed
- is depended on by
-
SERVER-80135 Allow ShardCollection to work correctly when an unsharded collection is not located on the DBPrimary
- Closed
-
SERVER-83386 Enable feature flag for new CreateCollectionCoordinator
- Closed
- is related to
-
SERVER-83631 Create collection coordinator must rollback if it finds an error when recreating chunk distribution
- Closed
-
SERVER-83637 Ensure that create collection coordinator does not create a collection in non involved shards
- Closed
-
SERVER-83387 Increase test coverage for concurrent create collection with addZone/removeZone
- Backlog
-
SERVER-83388 Increase test coverage for concurrent create collection with addShard/removeShard
- Backlog
-
SERVER-79304 Remove Pre 7.3 compatible CreateCollectionCoordinator implementation once 8.0 becomes last LTS
- In Progress
-
SERVER-79015 Create a feature flag to protect our new implementation of createCollection.
- Closed
-
SERVER-79052 Add a new version of the create collection coordinator
- Closed
-
SERVER-79151 Rename legacy CreateCollectionCoordinator and create new skeleton
- Closed
-
SERVER-79246 Remove config.system.session check
- Closed
-
SERVER-79299 Drain 'shardCollections' as part of the setFCV process.
- Closed
-
SERVER-79300 Add precondition checks to createCollection coordinator
- Closed
-
SERVER-79406 Consider skipping the rest of the chain if the collection is already sharded.
- Closed
-
SERVER-79491 Define CreateCollectionCoordinator phases
- Closed
-
SERVER-79829 Potentially change `migration_server_status.js` to work with CreateCollection_v4
- Closed
-
SERVER-79963 Make the authoritative shardCollection DDL coordinator resilient to unrecoverable errors and step down events
- Closed
-
SERVER-79964 Shards participating in the authoritative shardCollection should have up-to-date filtering information before the critical section is released
- Closed
-
SERVER-79965 Optimise the authoritative shardCollection to only block writes on shards that are going to own data
- Closed
-
SERVER-79966 Enable the testing of the Authoritative shardCollection in all_feature_flags test suites
- Closed
-
SERVER-80857 Introduce a new section for the shardCollection to the Sharding README
- Closed
-
SERVER-79826 Make create collection coordinator target only the involved shards
- Closed
-
SERVER-83497 Simplify commit function for the new create collection coordinator
- Closed