[SERVER-30533] v3.2 config primary does not release the balancer distlock on step up, and thus the balancer lock is held until timeout on downgrade from v3.4 => v3.2 Created: 07/Aug/17  Updated: 06/Dec/22  Resolved: 09/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding
Participants:

 Description   

We could fix this by adding sharding step up logic to the config server to release the balancer distributed lock if it is held by the config Balancer.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 07/Aug/17 ]

Should probably extend this to unlock all distlocks that the config holds, not just the balancer distlock, as v3.4 does. I imagine collection distlocks are also causing trouble, taking 15 minutes to time out, but just not being noticed because it's more subtle.

Generated at Thu Feb 08 04:24:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.