[SERVER-39468] renameCollection can potentially conflict with shardCollection Created: 08/Feb/19  Updated: 29/Oct/23  Resolved: 21/Apr/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.1.7
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-55637 Create random_DDL_CRUD_setFCV_operati... Closed
Related
is related to SERVER-39464 Concurrent rename and shard collectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Currently renameCollection is just a passthrough command and does not involve the config server or take any distributed lock. This can potentially mess up the config metadata if it runs concurrently with shardCollection.



 Comments   
Comment by Githook User [ 21/Apr/21 ]

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-39468: Take distLocks on legacy renameCollection
Branch: master
https://github.com/mongodb/mongo/commit/c90de3e65fff76ead7b8ca4664c3f34b0c913e04

Generated at Thu Feb 08 04:52:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.