[SERVER-56994] Do not interrupt ShardingDDLCoordinator instances before releasing distributed locks Created: 17/May/21 Updated: 29/Oct/23 Resolved: 17/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | Backlog |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2021-05-17 |
| Participants: |
| Description |
|
Failed sharding DDL coordinators that didn't managed to write their state document on disk are explicitly de-registered from the in-memory registry by calling POS::releaseInstance(). |
| Comments |
| Comment by Githook User [ 17/May/21 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |