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

multiple connections to shards can rarely get mutually inconsistent versions when migrate occurs

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.1.0
    • Affects Version/s: 2.1.0
    • Component/s: Sharding
    • None
    • ALL

      ...think this has to do with migration triggered from the same mongos, so version is auto-reloaded afterward.

      Sample bigMapReduce.js that fails - one of the connections has a stale version compared to the current version.

        1. mr_output_that_fails.txt
          1.35 MB
          Greg Studer

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

              Created:
              Updated:
              Resolved: