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

Consider increasing default distributed lock timeout

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: 3.4.17
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Linked BF Score:
      13

      Description

      The default timeout for grabbing the distributed lock is 20 seconds and in test suites with CSRS stepdowns, attempts to take the lock can time out and fail tests, especially on slower platforms.

      This is more of an issue in earlier releases, like 3.4, where more metadata commands run on mongos.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              jack.mulrow Jack Mulrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: