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

MigrationSourceManager::getMigrationStatusReport must expect optional max bound

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc4, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v6.0
    • Sharding EMEA 2022-05-02
    • 0

      With the moveRange introduction, the MigrationSourceManager is calculating and initializing the max bound after its constructor is invoked.
      It then can happen that getMigrationStatusReport gets called before the attribute is instantiated since the server status command is periodically invoked.

      Objectives of the ticket:

      • Change this line to _args.getMax().value_or(BSONObj())
      • Put the following TODO on the line right before in order to not incur in the same problem when making min optional: // TODO SERVER-64926 do not assume min always present

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: