[SERVER-54456] Fix resharding class mutex handling at time of PrimaryOnlyService instance completion Created: 10/Feb/21 Updated: 29/Oct/23 Resolved: 25/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Blake Oler | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M2.5, PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2021-02-22, Sharding 2021-03-08 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
In resharding services, the mutex is held at completion time for longer than the explicit purpose of protecting the member promises. In these locations, reduce the scope of the mutexes to only protecting the promises. The current over-extension of these mutexes causes contention when trying to call interrupt(). Locations: |
| Comments |
| Comment by Githook User [ 25/Feb/21 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: |