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

make multi-shard retrying due to stale versions smarter

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None

    Description

      In general, when doing multi-shard operations which depend on versions, if a single or only two shards have incorrect versions the command / query needs to be retried on all shards. This is not usually necessary, and can cause unnecessary load if the command is costly (like mapreduce).

      Fix : figure out which shards we need to refresh, just retry commands on those servers. This wouldn't totally eliminate the problem (if detected a version change on one shard but not the other after a migrate, for example), but would make it much less likely.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: