moveChunk aborted but still trying on shard

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Spencer Brody (Inactive)
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: