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

Consider increasing default distributed lock timeout

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.17
    • Component/s: Sharding
    • None
    • Sharding
    • 13

      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.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: