[SERVER-42360] cleanupOrphaned does not work properly in edge case with concurrent migrations on a shard 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_incoming_and_outgoing_repro.js     File cleanup_orphaned_parallel_migration_repro.diff    
Issue Links:
Depends
depends on SERVER-42473 Create concurrency workload to valida... Closed
Related
related to SERVER-42352 cleanupOrphaned does not respect migr... Closed
is related to SERVER-42473 Create concurrency workload to valida... Closed
Assigned Teams:
Sharding EMEA
Operating System: ALL
Participants:

 Description   

When a shard has an incoming and an outgoing migration for the same collection on the same shard, cleanupOrphaned does not work properly. Repro attached.

Affects all 4.2 and earlier versions. 

In 4.4 with Resumable range deleter on with FCV=4.4, this is no longer an issue. 



 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:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.