-
Type: Task
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
Sharding EMEA
We should be trying to avoid doing blocking work in the stepUp path as much as possible. The balancer, however, does a blocking wait for the previous balancer run to complete, as well as a database i/o as part of stepup.
Instead, the balancer's onStepUpComplete method should schedule a thread to do this work asynchronously, without blocking stepup.
- is depended on by
-
SERVER-49532 Remove OperationContext argument from ReplicaSetAwareService::onStepUp methods
- Backlog
-
SERVER-49534 Remove ReplicaSetAwareService::onStepUpBegin
- Backlog