Append error reporting to the removeShard response

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket is related to SERVER-107892 . According to this section in the Atlas scope, we need the following addition in the server's response:

      Enhanced error reporting: Currently these errors are present in the config.changelog, we will have to append it to the response.

      Granular error reporting with detailed information at the collection level to be added to the removeShard response.

      "migrationErrors": {    "count": 2,    "details": [      {        "Namespace": "db2.collectionA",        "chunkRange": { "min": { "key": "A" }, "max": { "key": "B" } },        "reason": "Chunk too large for migration"      },      {        "Namespace": "db2.collectionB",        "chunkRange": { "min": { "key": "100" }, "max": { "key": "200" } },        "reason": "Write activity retrying migration"      }    ]  }

            Assignee:
            Unassigned
            Reporter:
            Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: