[SERVER-58991] Acquire the critical section on the recipient shard of a moveChunk operation Created: 01/Aug/21  Updated: 29/Oct/23  Resolved: 13/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: PM-2423-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-59965 Distributed deadlock between renameCo... Closed
is depended on by SERVER-58992 Force a refresh of the filtering meta... Closed
Related
related to SERVER-60645 Recoverability of recipient shard cri... Closed
related to SERVER-60984 Report time in recipient critical sec... Closed
is related to SERVER-60415 No longer accept FailPointSetFailed e... Closed
is related to SERVER-60982 Evaluate the performance of the new m... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-08-09, Sharding EMEA 2021-08-23, Sharding EMEA 2021-09-06, Sharding EMEA 2021-09-20, Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
Participants:

 Description   

The acquisition of the critical section should happen once the recipient has the up to date version of the documents of the chunk being migrated.

We should block write operations on the recipient shard.

This ticket only deals with the happy-path (i.e. non failover). The failover recovery will be addressed in a follow-up ticket (SERVER-60645).



 Comments   
Comment by Githook User [ 13/Oct/21 ]

Author:

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

Message: SERVER-58991 Acquire the critical section on the recipient shard of a moveChunk operation (happy-path)
Branch: master
https://github.com/mongodb/mongo/commit/9f0021aeb386304be5b1a538dae0e9172754aa90

Generated at Thu Feb 08 05:46:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.