Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Works as Designed
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication, Sharding
Labels:
None

Assigned Teams:

Sharding EMEA
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: [DO NOT USE] Backlog - Sharding EMEA
Reporter:: Spencer Brody (Inactive)
Participants:: [DO NOT USE] Backlog - Sharding EMEA, Judah Schvimer, Kaloian Manassiev, Spencer Brody, Tess Avitabile
Votes:: 0 Vote for this issue
Watchers:: 11 Start watching this issue

Created:: Jul 15 2020 08:47:24 PM UTC
Updated:: Oct 27 2023 01:52:47 PM UTC
Resolved:: Nov 15 2021 03:15:09 PM UTC