Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-59495

Update recipient state machine depending on featureFlagSliceMerge

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0
    • 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)

            suganthi.mani@mongodb.com Suganthi Mani
            jesse@mongodb.com A. Jesse Jiryu Davis
            0 Vote for this issue
            4 Start watching this issue