The recovery of the shard version and the migration in the moveChunk should be done in a separate thread

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
    • 137
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-62282 added a recovery of the shard version and migrations until it suceeds. The problem is that we are running it on the same thread that was executing the different phases of the moveChunk on the donor. This could produce a deadlock, which is very well described in BF-24170.

            Assignee:
            Antonio Fuschetto
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: