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

Migration distlock acquisition fails to catch status

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.0
    • Sprint:
      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
    • Linked BF Score:
      127

      Description

      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.
       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kaloian.manassiev Kaloian Manassiev
              Reporter:
              blake.oler Blake Oler
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: