Split donor should wait for blockTimestamp to be majority committed on donor nodes before sending splitConfig

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Serverless
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Right now the split donor waits for blockTimestamp to get applied on all recipient nodes, then sends the splitConfig.

      I think the donor should also wait for blockTimestamp to become majority committed in the donor set before sending the splitConfig.

      Otherwise the donor could fail over and the new donor primary can choose a new blockTimestamp and try waiting for it to get applied on all recipient nodes, but the recipient nodes are already gone. The donor may hang or abort the split in this case today.

            Assignee:
            [DO NOT USE] Backlog - Server Serverless (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: