[SERVER-56956] ScopedShardVersionCriticalSection can leave critical section held if filtering metadata refresh fails Created: 14/May/21 Updated: 29/Oct/23 Resolved: 18/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.0.0 |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 38 | ||||||||
| Description |
|
If the ScopedShardVersionCriticalSection constructor enters the critical section catchUp phase, but later forceShardFilteringMetadataRefresh fails, the critical section will be left taken because it's constructor won't execute. |
| Comments |
| Comment by Githook User [ 18/May/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |