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

acquiring distributed lock for upgrade process for 2.2->2.4 has very long timeout.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0-rc2
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      if the distributed lock to initiate the upgrade process can not be acquired for some reason (e.g. a config server is down) it continues to retry for up to 15 mins before failing completely.
      for upgrade process we might want to make this fail more quickly so that it is clearer to the user what is happening, otherwise it is a bit concerning to see an upgrade process spam the logs with lots of lock acquisition failure messages.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              greg_10gen Greg Studer
              Reporter:
              mpobrien Michael O'Brien
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: