[SERVER-56561] create collection coordinator release critical section unconditionally on stepdown Created: 02/May/21 Updated: 29/Oct/23 Resolved: 05/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: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2021-05-03, Sharding EMEA 2021-05-17 | ||||||||
| Participants: | |||||||||
| Description |
|
The create collection coordinator always release the collection critical section when the node is stepping down. This is wrong because we could have multiple coordinators waiting to acquire the distributed lock in addition to the one that is actually being executed. In case of stepdown the the coordinators that are waiting will release the critical section while there is a running coordinator that requires it. |
| Comments |
| Comment by Githook User [ 04/May/21 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |