[SERVER-74035] Make the `_shardsvrMovePrimaryExitCriticalSection` command idempotent Created: 15/Feb/23  Updated: 29/Oct/23  Resolved: 21/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: PM-2144-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06
Participants:
Linked BF Score: 135

 Description   

The _shardsvrMovePrimaryExitCriticalSection command is used in the context of the movePrimary command by the donor to ask the recipient to exit its critical section.

There are situation where the command reply is not received by the donor, although the critical section was actually exited. The critical section (on the recipient) could be re-entered by another operation, and the second call attempt from the donor could fail since the passed reason differs from the one of the entered critical section.

One goal of this ticket is make the _shardsvrMovePrimaryExitCriticalSection command idempotent (in the end the passed critical section is actually exited).

 



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

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-74035 Make the `_shardsvrMovePrimaryExitCriticalSection` command idempotent
Branch: master
https://github.com/mongodb/mongo/commit/62c3f0c89a530631f479ab19b1ac32f7c53e21dc

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