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

XMLWordPrintableJSON

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

      ...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

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: