[SERVER-56612] Use the resharding-specific refresh function when recovering a resharding operation in the drain mode Created: 04/May/21  Updated: 29/Oct/23  Resolved: 10/May/21

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

Type: Bug Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Sergi Mateo Bellido
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-56638 Fix flushReshardingStateChanges criti... Closed
is related to SERVER-53653 [Resharding] Take the critical sectio... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2021-05-17
Participants:

 Description   

When we recover the resharding ops in the drain mode we do a refresh of the collection. This refresh may hang here, because the in-memory critical section was already retaken and it will be released once the resharding operation is completed.

The proposed solution is calling this resharding-specific function instead of the generic one.

This issue was introduced when we replaced the in-memory critical sections by recoverable critical sections in SERVER-53653.



 Comments   
Comment by Githook User [ 10/May/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-56612 Use the resharding-specific refresh function when recovering a resharding operation in the drain mode
Branch: master
https://github.com/mongodb/mongo/commit/c456a6ba624cb4dfb97a4afaba59200e3c8cb8ae

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