[SERVER-65387] Ensure that resumeMigrationCoordinationsOnStepUp() does not interfere with ongoing migrations Created: 08/Apr/22  Updated: 27/Oct/23  Resolved: 11/Apr/22

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

Type: Bug Priority: Major - P3
Reporter: Paolo Polato Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:
Linked BF Score: 135

 Description   

 SERVER-64979 introduce a change to make the execution of resumeMigrationCoordinationsOnStepUp() asynchronous.
This may raise issues if the resumed migrations concerns collections that are currently being involved in R/W operations or chunk migration requests, since such function contains logic to invalidate the collection filtering metadatata.

(One example is the activation of this invariant, as observed in BF-24833).



 Comments   
Comment by Allison Easton [ 11/Apr/22 ]

Closing this ticket because SERVER-64979 has been reverted

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