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

moveChunk aborted but still trying on shard

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • ALL

    Description

      changelog shows moveChunk aborted, but db.currentOp() shows an active moveChunk for those same ranges. The logs go from showing progress on that migration to suddenly logs from a moveChunk with all the data is empty/zeroes. See linked CS ticket comments from Dec 30 for more info.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: