[SERVER-30220] Lock correct nss for syncApply by UUID Created: 18/Jul/17  Updated: 30/Oct/23  Resolved: 19/Jul/17

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 3.5.11

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-30293 in syncApply, throw NamespaceNotFound... Closed
related to SERVER-30521 in syncApply, throw NamespaceNotFound... Closed
related to SERVER-33160 syncApply() treatment of delete opera... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-07-31
Participants:

 Description   

When re-applying operations on a collection with a UUID after renaming it, syncApply has too ensure that it will lock using the actual name for the collection identified by the UUID.



 Comments   
Comment by Githook User [ 19/Jul/17 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-30220 Lock correct nss for syncApply by UUID
Branch: master
https://github.com/mongodb/mongo/commit/9d8bc8dc6c8d1dc92bbf466f27783464ed4f5704

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