Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Diagnostics, Sharding
Labels:

Assigned Teams:

Cluster Scalability
Case:
Story Points:
3
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

Currently, if a donor shard fails an ongoing migration, it will not include the error, which caused the failure, which makes it difficult to diagnose such failures. Whenever possible, if a migration fails we should include the reason for the failure.

It might be most practical to do this in the destructor of MoveChunkHelper if it is possible to read what was the last exception thrown there.

Assignee:: [DO NOT USE] Backlog - Cluster Scalability
Reporter:: Kaloian Manassiev
Participants:: [DO NOT USE] Backlog - Cluster Scalability, Josef Ahmad, Kaloian Manassiev
Votes:: 2 Vote for this issue
Watchers:: 12 Start watching this issue

Created:: Oct 02 2018 10:18:51 AM UTC
Updated:: Aug 01 2025 04:30:32 PM UTC

Details

Description

Attachments

Forms

Activity

People

Dates