[SERVER-73388] RenameCollection can attempt to release critical section after migration are already resumed. Created: 27/Jan/23  Updated: 29/Oct/23  Resolved: 23/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-43099 Reenable random chunk migration failp... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-03-06
Participants:
Story Points: 4.5

 Description   

RenameCollection stops migrations here and they are reenabled here as part of the commit to the configsvr. At this point, the balancer can start issuing migrations, although they'll get blocked behind the shards critical section. As soon as the critical section is released, migrations can start.

The problem is that the UnblockCRUD phase may need to be repeated in case of participant stepdown. At that point, a migration could have started, and the rename operation would hit this tassert when attempting to release the critical section (that had already released, and the migration has taken now)



 Comments   
Comment by Githook User [ 23/Feb/23 ]

Author:

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

Message: SERVER-73388 Do not fail renameParticipant if it encounters a critical section with different reason when attempting to release it.
Branch: master
https://github.com/mongodb/mongo/commit/b226016300037acfe32578255de89a14631d1d6c

Generated at Thu Feb 08 06:24:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.