-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
As seen in BF-39078, the aggressive failover testing is overloading the locust primary's cpu causing the the workload to timeout while waiting for the resharding operation to finish. The following improvements should be considered to decrease the load:
- decrease number of read and write users
- remove priority on the config server to avoid extra failovers
- reduce cadence of stepdowns on config server