backport of targeted shard ranges instead of broadcast on all queries

XMLWordPrintableJSON

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

      We shouldn't ever send queries to shards where the collection does not exist - this can introduce version issues (since version 0 is "special") and cause problems when dropping shards (since the dropped shards are also targeted until refreshed).

      Proposing backport of f93918db (partial or full) - we previously didn't backport b/c potentially a bit dangerous, but has not caused any problems in master for several months, so it's probably burned-in enough.

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

                Created:
                Updated:
                Resolved: