[SERVER-55976] Orphans check at the end of jstest can fail in presence of concurrent drop collection Created: 09/Apr/21 Updated: 29/Oct/23 Resolved: 12/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| 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: | 35 | ||||
| Description |
|
If the orphans check runs concurrently with the drop, finds an entry in config.collections here, but later it queries config.collections again as part of findChunksUtil.findChunksByNs (to decide whether to join the config.chunks by 'ns' or 'uuid'), but now the collection entry has already been deleted by the drop, so it fails. |
| Comments |
| Comment by Githook User [ 12/Apr/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |