Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-84303

Give a better indication of why a moveChunk operation has failed

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability
    • 3

    Description

      When moving a chunk we rely on IndexCatalog::removeExistingIndexesNoChecks to determine if the indexes are the same between the source and destination. Upon inspecting why the exception occurred in a customer case it seemed like both sides had the same indexes when using commands such as getIndexes. This ticket is to improve this situation such that we are given better diagnostic information in the error or getindexes output.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            lamont.nelson@mongodb.com Lamont Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: