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

Use higher wtimeout in catalog_shard.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5
    • 30

      catalog_shard.js passes a wtimeout with the config shard transition commands to verify it accepts them, but uses a relatively small value - 100ms - which can be exceeded on slow platforms. We can keep the same coverage and avoid failures by using a much higher timeout, like 1 day.

            Assignee:
            jack.mulrow@mongodb.com Jack Mulrow
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: