[SERVER-47237] Add the "Shard versioning and database versioning" section to the sharding arch guide Created: 01/Apr/20  Updated: 29/Oct/23  Resolved: 04/May/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-04, Sharding 2020-05-18
Participants:

 Description   

Guidelines:

Should include

  • What does the versioning protocol achieve? E.g., allows a router to lazily discover that its routing cache is stale
  • What types of events cause a routing cache to be stale?
  • What are special version conventions we use? 0,0|0 for unsharded, 0,0|epoch for no chunk, 0,0|MAX for ignored

Code references

  • Where shardVersions are stored in a router's cache
  • An example of how shardVersion is attached in an egress message
  • Where shardVersions are parsed in the ServiceEntryPoint and put on the OperationShardingState
  • Where shardVersions are stored in a shard's filtering cache
  • The checkShardVersion method on a shard


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

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-47237 Add the "Shard versioning and database versioning" section to the sharding arch guide
Branch: master
https://github.com/mongodb/mongo/commit/29d18dc44fb9ae5054c8e269d6a3cafcc46c2899

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