[SERVER-31352] Always skip OperationShardingState initialization if the read concern is `available` Created: 02/Oct/17  Updated: 30/Oct/23  Resolved: 05/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-10-23
Participants:
Linked BF Score: 0

 Description   

Currently, the check for shard version mismatch consults both the operation's state (when shardVersion parameter is attached to the command) and the connection's sharding info (when the command is run over a sharded collection).

Instead of looking up one or the other at version check time, we should consolidate the code which determines what shardVersion a request must use to happen in one place so that we can add additional checks that for example requests over sharded connections do not contain shard version.



 Comments   
Comment by Githook User [ 05/Oct/17 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-31352 Always skip OperationShardingState initialization if readConcern is `available`
Branch: master
https://github.com/mongodb/mongo/commit/ed31e32a74d942ef337ef507ad4628d224d65953

Generated at Thu Feb 08 04:26:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.