[SERVER-21766] Remove waiting for balancer lock behavior from sh.startBalancer Created: 04/Dec/15  Updated: 06/Dec/22  Resolved: 14/Dec/15

Status: Closed
Project: Core Server
Component/s: Sharding, Shell
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-19467 Race in sh.startBalancer() Closed
related to DOCS-1555 sh.startBalancer() might be the wrong... Closed
is related to DOCS-6721 Recommend sh.startBalancer() over sh.... Closed
is related to SERVER-22463 sh.startBalancer should be smarter ab... Closed
Assigned Teams:
Sharding
Participants:

 Description   

In DOCS-1555 we changed our recommendations for users starting the balancer from using sh.startBalancer() to sh.setBalancerState(true) because the former waits for a mongos to take the balancer lock after enabling the balancer. If we're not recommending that people use sh.startBalancer() because of this behavior, we should probably just remove that behavior so that sh.startBalancer does what we want it to.


Generated at Thu Feb 08 03:58:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.