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

Migration status reports verify connection strings -- but those can change

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.3, 4.1.3
    • Affects Version/s: 4.0.1
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.0
    • Sharding 2018-09-10
    • 17

      During the chunk migration process, the source shard periodically polls the destination shard for updates. As part of the information verification process, we verify that the source shard's connection string hasn't changed. However, valid situations exist where it might change. For example, adding a new node to the source shard's replica set would change the connection string but would not change the behavior of that shard with regards to migrations.

      Failures have cropped up where shards are aborted because the connection string has changed. Instead, we should verify that the from shard's name hasn't changed. Shard names are immutable and will serve to verify a shard without error.

      The line of code to change is here.

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            blake.oler@mongodb.com Blake Oler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: