inserts need better handling of version changes

XMLWordPrintableJSON

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

      In at least certain cases, inserts do not re-check the shard they were sent to when receiving a bad version in checkShardVersion. This can lead to misdirected inserts if migrations are heavy, particularly if migrations are taking a lot of resources. (this, along with SERVER-4603, may be impacting mrShardedOutput.js/bigMapReduce.js).

      Solution - probably refactor this code in line with the new pcursor stuff.

        1. insert_during_migrate.js
          4 kB

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

                Created:
                Updated:
                Resolved: