[SERVER-50507] Avoid race conditions during recoverRefreshShardVersion Created: 25/Aug/20 Updated: 29/Oct/23 Resolved: 04/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-1 | ||
| 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: | 27 | ||||||||
| Description |
|
Currently, there is no warranty that a collection state is not going to change after refreshing its filtering metadata and before acquiring the lock to cleanup the recover/refresh future. The forceShardFilteringMetadataRefresh call should ideally be replaced by a method not acquiring locks, in order to not serialize other collection operations on it. |
| Comments |
| Comment by Githook User [ 04/Sep/20 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Pierlauro Sciarelli [ 28/Aug/20 ] |
|
Depends on |