-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Diagnostics, Sharding
-
Cluster Scalability
-
(copied to CRM)
-
3
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.