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

Add more info in currentOp when moveChunk is in 'join' mode

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 3.4.0-rc0
    • Diagnostics, Sharding
    • None
    • Sharding
    • ALL

    Description

      For debuggability and to differentiate between moveChunk commands that are actually doing work from ones that are waiting for another moveChunk command to complete. One possible way to do this is to use CurOp::setMessage_inlock.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: