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

Recipient garbarge collects itself on primary step up

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Server Serverless 2022-03-07, Server Serverless 2022-03-21

    Description

      When a recipient primary steps up after a split, it will have a local out-of-date state document for the split which it originates from. When the recipient starts an instance for this state document and observes that the state is kBlocking and the local set name is equal to the stored recipientSetName, then the recipient should abort the current operation and delete the state document. We should make sure that this method is written generically to support additional cleanup if needed.

      Attachments

        Activity

          People

            mathis.bessa@mongodb.com Mathis Bessa
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: