-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Server Serverless 2021-09-27, Server Serverless 2021-10-04, Server Serverless 2021-10-11, Server Serverless 2021-10-18, Server Serverless 2021-10-25, Server Serverless 2021-11-01, Server Serverless 2021-11-15
-
182
Add a "protocol" field with a string value of either "multitenant migration" or "slice merge". We initially choose a protocol based on whether slice merge is enabled (see above), then persist this choice in the state machine and use the state machine to determine the protocol in later steps.
Make tenant id optional (if Merge is enabled it must be absent, otherwise it must be a string).
UPDATE: This ticket does the following things.
1) Update donor state machine depending on featureFlagSliceMerge (SERVER-59494)
2) Update recipient state machine depending on featureFlagSliceMerge (SERVER-59495)
3) Add protocol & tenant id optional in recipientSyncData command. (SERVER-59787)
- causes
-
SERVER-61272 Coverity analysis defect 121076: Uninitialized scalar field
- Closed
-
SERVER-61226 Dead code in shard_merge_enabled.js
- Closed
- depends on
-
SERVER-61288 idl_check_compatibility.py parses older version command idl files using files imported from master source
- Closed
-
SERVER-61129 Recipient state machine changes for Merge
- Closed
- is depended on by
-
SERVER-61128 Implement voteCommitMergeProgress command
- Closed
-
SERVER-61581 Determine TenantMigration{Donor,Recipient}Service coordination mechanism
- Closed
-
SERVER-63397 Abort all donor index builds
- Closed