Migration distlock acquisition fails to catch status

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v5.0
    • Sharding 2021-04-05, Sharding EMEA 2021-05-03, Sharding EMEA 2021-05-17, Sharding EMEA 2021-05-31, Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28
    • 127
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      During scheduling a migration, we attempt to acquire the local distlock for the namespace. This acquisition isn't exception-safe – in particular, in can throw LockBusy.

      We don't attempt to catch this exception (unlike in the next dist-lock acquisition, where we check the status then just return).

      As a result of this uncaught exception, the balancer thread will crash, terminating the whole process.
       

              Assignee:
              Kaloian Manassiev
              Reporter:
              Blake Oler
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: