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

Record MoveChunk UID

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 2

      Currently there is no simple way to correlate the moveChunk documents recorded in config.changelog to the same moveChunk action.

      Would be easier if we have UID per moveChunk.

            Assignee:
            Unassigned Unassigned
            Reporter:
            renato.riccio@mongodb.com Renato Riccio
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: