[SERVER-52621] Remove stale version execption handling in OpQuery exec path Created: 04/Nov/20  Updated: 29/Oct/23  Resolved: 06/Nov/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Minor - P4
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: PM-1965-Milestone-0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Sprint: Sharding 2020-11-16
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 06/Nov/20 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-52621 Remove stale version execption handling in OpQuery exec path
Branch: master
https://github.com/mongodb/mongo/commit/640a850162bfe814444b35a8b2143f78ae40e20d

Generated at Thu Feb 08 05:28:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.