Remove stale version execption handling in OpQuery exec path

XMLWordPrintableJSON

    • Minor Change
    • Sharding 2020-11-16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Stale version exceptions are currently handled [1, 2] in the OpQuery execution path on mongod.

      This is superfluous because:
       - A client contacting directly a shard's node won't participate in the versioning protocol and thus won't trigger any stale version exceptions.
       - Mongos does not use the OpQuery path anymore to query the shards, It instead uses the find command.

              Assignee:
              Tommaso Tocci
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: