[SERVER-50288] Return collection version on split and merge commands Created: 13/Aug/20  Updated: 29/Oct/23  Resolved: 04/Sep/20

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

Type: Improvement Priority: Minor - P4
Reporter: Marcos José Grillo Ramirez Assignee: Pierlauro Sciarelli
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-09-07
Participants:
Linked BF Score: 5

 Description   

SERVER-46199 introduces a causally consistent catalog cache, which, among other consistency improvements, also optimizes the number of round trips to the config server after detecting a router is stale and needs to advance the local shard version.

Another improvement can be achieved by returning the resulted collection version on the split chunk and merge chunks commands, because instead of fully invalidating the cache after splitting or merging, we could simply advance the shard version which in turn would only request the diff of the changes instead of a full chunk request.



 Comments   
Comment by Githook User [ 04/Sep/20 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-50288 Return collection version on split and merge commands
Branch: master
https://github.com/mongodb/mongo/commit/74756b18f43407e32496b600f2466457c59cb26a

Comment by Kaloian Manassiev [ 14/Aug/20 ]

FYI, this should be as simple as adding a call and returning the value of getShardAndCollectionVersion, which will make the response match that of _configsvrCommitChunkMigration.

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