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

Remove sleeps from the chunk migration recipient catch-up phases

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Sharding EMEA
    • Sharding EMEA 2021-05-31, Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28

      The chunk migration recipient side uses a "check opReplicatedEnough" / "sleep" kind of model to wait for replication during the CATCHUP phase. Same thing exists for the STEADY phase, where we check and then sleep.

      These should be switched to proper calls to waitForWriteConcern instead.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: