-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:None
-
Fully Compatible
-
Sharding EMEA 2022-03-21
The quiesce mode timeout is driven by the shutdownTimeoutMillisForSignaledShutdown server parameter that has a default value of 15 seconds.
This parameter is set to 100ms for all our fixtures that use replicasets except for the tenant migrations ones that stick to the default 15 sec value.
As a consequence all suites that use this fixture require very long time to run on evergreen. By reducing this timeout also for tenant migration fixture I managed to drastically reduce test runtime for those suites.
- tenant_migration_jscore_passthrough
- 1 h -> 15 min
- tenant_migration_causally_consistent_jscore_passthrough
- 1 h -> 15 min
- tenant_migration_multi_stmt_txn_jscore_passthrough:
- 4 h 45 min -> 30 min
- tenant_migration_stepdown_jscore_passthrough:
-
- 3h 51 min -> 30 min
- tenant_migration_kill_primary_jscore_passthrough:
- 3h 30 min -> 30 min
- tenant_migration_terminate_primary_jscore_passthrough:
- 4h 15 min -> 30 min
- is caused by
-
SERVER-63266 Support starting a replica set node without an initial setName
- Closed