[SERVER-59494] Update donor state machine depending on featureFlagSliceMerge Created: 20/Aug/21  Updated: 03/Nov/21  Resolved: 15/Oct/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Suganthi Mani
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-60688 IDL compiler doesn't generate include... Closed
Related
related to SERVER-60757 Complete TODO listed in SERVER-59494 Closed
related to SERVER-60866 Complete TODO listed in SERVER-59494 Closed
Sprint: Server Serverless 2021-09-13, Server Serverless 2021-09-20, Server Serverless 2021-09-27, Server Serverless 2021-10-04, Server Serverless 2021-10-11, Server Serverless 2021-10-18
Participants:

 Description   

Add a "pinning" state (see Pinning the oldest timestamp).
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).
+

Also make tenantId arg of donorStartMigration optional.



 Comments   
Comment by Suganthi Mani [ 15/Oct/21 ]

This work is taken care by SERVER-59495.

Comment by A. Jesse Jiryu Davis [ 27/Sep/21 ]

Might not need "pinning" state if we don't do oldest timestamp coordination

Generated at Thu Feb 08 05:47:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.