[SERVER-75747] MovePrimaryRecipient Must Clear DbInfo Before Releasing Critical Section Created: 06/Apr/23  Updated: 29/Oct/23  Resolved: 07/Apr/23

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

Type: Bug Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Abdul Qadeer
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding NYC 2023-04-17
Participants:
Story Points: 2

 Description   

With OnlineMovePrimaryLifecycle enabled, the recipient manages its own critical section instead of relying on commands sent by the coordinator. The ShardsvrMovePrimaryExitCriticalSectionCommand clears the database info on the recipient node before releasing the critical section, but the MovePrimaryRecipient currently does not do this.

A possible fix is on the test branch here.



 Comments   
Comment by Githook User [ 07/Apr/23 ]

Author:

{'name': 'Abdul Qadeer', 'email': 'abdul.qadeer@mongodb.com', 'username': 'zorro786'}

Message: SERVER-75747 Clear database metadata before releasing CS
Branch: master
https://github.com/mongodb/mongo/commit/d7e04f8258e2e798602368958974e78bfc1ab288

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