Increase reshardingCriticalSectionTimeoutMillis for store_historical_placement_data.js

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0, 7.2.0-rc2, 7.0.5
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v7.2, v7.0
    • CAR Team 2023-11-27
    • 5
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a resharding operation is initiated without using ReshardingTest fixture, we need to increase the critical section timeout due to possible slow network/machines in test infra. The value we use in the fixture is:

      ```
      criticalSectionTimeoutMS: criticalSectionTimeoutMS = 24 * 60 * 60 * 1000 /* 1 day */,
      ```

      A sample change in ShardingTest present below:

      https://github.com/10gen/mongo/pull/13554

              Assignee:
              Aitor Esteve Alvarado
              Reporter:
              Abdul Qadeer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: