Include the cause for migration failure on the donor shard in the changelog

XMLWordPrintableJSON

    • Cluster Scalability
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • 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
            Votes:
            2 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: