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

updates need better handling of version changes (sharding_balance4.js failure)

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • ALL

      Because the chunk manager used to determine the shard to send updates to is not necessarily the same as the chunk manager used to verify an up-to-date version for the shard connection used in an update, it's possible for the chunk manager to be changed in the meantime, resulting in an update being sent via an up-to-date connection to the wrong shard.

      Problem and fix is essentially the same as for SERVER-4604, but for updates.

      Manifests in http://buildbot.mongodb.org/builders/Linux%2064-bit%20DUR%20OFF/builds/1073/steps/test_1/logs/stdio/text

            Assignee:
            Unassigned Unassigned
            Reporter:
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: