[SERVER-49734] The call to Balancer::initiateBalancer() on step up should be asynchronous Created: 20/Jul/20  Updated: 29/Oct/23  Resolved: 17/Aug/20

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

Type: Bug Priority: Major - P3
Reporter: Alexander Taskov (Inactive) Assignee: Alexander Taskov (Inactive)
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-only, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-07-27, Sharding 2020-08-10, Sharding 2020-08-24
Participants:
Linked BF Score: 14

 Description   

The call to Balancer::initiateBalancer() is made fromĀ 
ReplicationCoordinatorExternalStateImpl::onTransitionToPrimary() however, some paths require majority write concern which cannot be satisfied until the stepup has completed. initiateBalancer should be called asynchronously to prevent deadlock.



 Comments   
Comment by Githook User [ 17/Aug/20 ]

Author:

{'name': 'Alex Taskov', 'email': 'alex.taskov@mongodb.com', 'username': 'alextaskov'}

Message: SERVER-49734 Used local write concern to cleanup active migration on config serveron stepup

(cherry picked from commit e6bfa33284b2c6a911df33e032eb1430326681d2)
Branch: v4.4
https://github.com/mongodb/mongo/commit/2f8d77c94b076062bf36b1f0a210ab42406635e8

Comment by Githook User [ 17/Aug/20 ]

Author:

{'name': 'Alex Taskov', 'email': 'alex.taskov@mongodb.com', 'username': 'alextaskov'}

Message: SERVER-49734 Used local write concern to cleanup active migration on config serveron stepup
Branch: master
https://github.com/mongodb/mongo/commit/e6bfa33284b2c6a911df33e032eb1430326681d2

Generated at Thu Feb 08 05:20:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.