[SERVER-54847] Ensure rename doesn't throw NamespaceNotFound once started Created: 01/Mar/21  Updated: 29/Oct/23  Resolved: 09/Mar/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Improvement Priority: Minor - P4
Reporter: Marcos José Grillo Ramirez Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2021-03-22
Participants:

 Description   

Right now a concurrent drop might run concurrently with a rename, causing the command to fail with NamespaceNotFound. This behaviour is fine and expected, however, we could check if the NamespaceNotFound came from the first check done on the command specifically, by checking for the changelog collection.



 Comments   
Comment by Githook User [ 09/Mar/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-54847 Ensure rename doesn't throw NamespaceNotFound once started
Branch: master
https://github.com/mongodb/mongo/commit/d7f2cc83a4cbdaa48f8196afaa03a72c3bb06d21

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