Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Gone away
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:
None

Assigned Teams:

Sharding EMEA
Operating System:
ALL
Sprint:
Sharding 2019-08-26
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

cleanup_orphaned_repro.js
4 kB
Jul 23 2019 04:02:35 PM UTC

depends on

SERVER-42473 Create concurrency workload to validate current cleanupOrphaned command and range deleter

Closed

is related to

SERVER-42360 cleanupOrphaned does not work properly in edge case with concurrent migrations on a shard

Closed

SERVER-42473 Create concurrency workload to validate current cleanupOrphaned command and range deleter

Closed

Assignee:: [DO NOT USE] Backlog - Sharding EMEA
Reporter:: Matthew Saltz (Inactive)
Participants:: [DO NOT USE] Backlog - Sharding EMEA, Cris Insignares Cuello, Matthew Saltz
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Jul 23 2019 04:00:21 PM UTC
Updated:: Oct 27 2023 08:42:46 PM UTC
Resolved:: Mar 03 2022 04:04:53 PM UTC