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

Remove MigrationReason from MigrateInfo

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-03-07, Sharding EMEA 2022-03-21
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, all MigrateInfos have a MigrationReason. However, the migration reasons are only used for returning the first compliance violation in the balancer status command. Instead of storing a MigrationReason for each MigrateInfo, we should return only the first violation reason separate from the MigrateInfoVector while running selectChunksToMove.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: