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

Wait for range deleter service to be fully initialized before transitioning to primary

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: 6.2.0-rc6
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v6.2
    • Sharding EMEA 2023-01-23
    • 0

      On step up complete, the range deleter service is asynchronously spawning the recovery of existing range deletions before setting its state as "up".

      Since the scheduling of new range deletions is disallowed while the service is not up, this may lead to errors in case a very fast migration commits (or simply when an already committed migration gets recovered).

      A possible solution to overcome this problem would be to spawn range deletion recovery when step-up begins and waiting for the component to be up before transitioning to primary.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: