[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:
Depends
Problem/Incident
is caused by SERVER-50056 Collections can become views during s... Closed
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: SERVER-50453 Handle NSS renaming when checking shard version in drop collection
Branch: master
https://github.com/mongodb/mongo/commit/e08eba28ab9ad4d54adb95e8517c9d43276e5336

Comment by Tommaso Tocci [ 25/Aug/20 ]

The bug has been introduced by SERVER-50056

Generated at Thu Feb 08 05:22:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.