[SERVER-20693] Stop including wanted and received chunk versions in StaleConfigExceptions Created: 29/Sep/15  Updated: 01/Oct/15  Resolved: 01/Oct/15

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

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-20676 Move chunk doesn't retry if the chunk... Closed
Sprint: Sharding A (10/09/15)
Participants:

 Comments   
Comment by Andy Schwerin [ 01/Oct/15 ]

That extra data is still required to control how much chunk data is reloaded by mongos on shard version exceptions.

Comment by Spencer Brody (Inactive) [ 30/Sep/15 ]

There is another place that references those values: https://github.com/mongodb/mongo/blob/r3.1.8/src/mongo/db/commands/write_commands/batch_executor.cpp#L182. The shardVersionWanted comes from the StaleConfigException (https://github.com/mongodb/mongo/blob/r3.1.8/src/mongo/db/commands/write_commands/batch_executor.cpp#L1022).
The "vWanted" written to the response by mongod is then used by mongos to selectively refresh the ChunkManagerTargeter: https://github.com/mongodb/mongo/blob/r3.1.8/src/mongo/s/chunk_manager_targeter.cpp#L587

Comment by Randolph Tan [ 30/Sep/15 ]

Note that the only place these values are actually referenced outside of logging is in parallel.cpp:

https://github.com/mongodb/mongo/blob/r3.1.8/src/mongo/client/parallel.cpp#L469

Generated at Thu Feb 08 03:55:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.