[SERVER-42352] cleanupOrphaned does not respect migration protocol on failover Created: 23/Jul/19  Updated: 27/Oct/23  Resolved: 03/Mar/22

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

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) 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

Attachments: File cleanup_orphaned_repro.js    
Issue Links:
Depends
depends on SERVER-42473 Create concurrency workload to valida... Closed
Related
is related to SERVER-42360 cleanupOrphaned does not work properl... Closed
is related to SERVER-42473 Create concurrency workload to valida... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Sprint: Sharding 2019-08-26
Participants:

 Description   

In a rare case, cleanupOrphaned does not behave properly when the destination shard fails over during migration. Repro attached.



 Comments   
Comment by Cris Insignares Cuello [ 03/Mar/22 ]

PM-1645 solved this issue. The effort to backport is too large, customer should upgrade to 4.4+.

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