[SERVER-50453] Handle NSS renaming when checking shard version in drop collection Created: 21/Aug/20 Updated: 29/Oct/23 Resolved: 25/Aug/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: | 34 | ||||||||||||
| Description |
|
When an index build is aborted due to the underlying collection getting dropped, there is currently a shard version check being executed on the namespace targeted by the drop command. However - since the collection could be renamed when temporarily releasing the locks - the check should be done on the new NSS after resolving it. |
| Comments |
| Comment by Githook User [ 25/Aug/20 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Tommaso Tocci [ 25/Aug/20 ] |
|
The bug has been introduced by |