Make sharding_csrs_continuous_config_stepdown use a larger defaultFindReplicaSetHostTimeoutMS and fassertOnLockTimeoutForStepUpDown when running on slow build variants

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability 19Jan-2Feb
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There have been multiple BFGs where tests in this suite time out on build variants because stepdown and stepup could take minutes to complete. This could fix this by increasing the failover interval and/or defaultFindReplicaSetHostTimeoutMS to save the retry overhead. The former was already recently increased from 8 seconds to 15 seconds in SERVER-116060. Increasing it further would risk lowering the test coverage for failovers in short tests. Therefore, we should increase only defaultFindReplicaSetHostTimeoutMS similar to what we did in SERVER-117465.

            Assignee:
            Cheahuychou Mao
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: