[SERVER-83230] Kill clone operation of move primary on cleanup Created: 14/Nov/23  Updated: 23/Nov/23  Resolved: 23/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Marcos José Grillo Ramirez Assignee: Backlog - Catalog and Routing
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-81229 Move primary may not cleanup cloned c... Closed
Assigned Teams:
Catalog and Routing
Participants:

 Description   

SERVER-81229 fix the correctness issue of move primary on stepdown, however, we still might have a clone operation that could take hours, which is unacceptable from an user perspective.

The purpose of this ticket is to investigate and implement a kill of the clone operation on the cleanup phase before dropping any leftover collection from a previous coordinator incarnation.



 Comments   
Comment by Cris Insignares Cuello [ 16/Nov/23 ]

sergi.mateo-bellido@mongodb.com to align with matt.panton@mongodb.com

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