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

Increase reshardingCriticalSectionTimeoutMillis for ShardingTest fixture

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5
    • 5
    • 1

      We have seen a lot of BFs arising from reshardingCriticalSectionTimeoutMillis timing out in test infra due to slower machines. A few examples include BF-30637, BF-30377, and BF-30354. To avoid more such coming up due to users issuing reshardCollection via ShardingTest fixture instead of ReshardingTest fixture, we should increase the default timeout internally inside ShardingTest fixture, while allowing any explicit override.

            Assignee:
            kruti.shah@mongodb.com Kruti Shah
            Reporter:
            abdul.qadeer@mongodb.com Abdul Qadeer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: