[SERVER-33453] Add timestamp support to the ChunkManager Created: 22/Feb/18  Updated: 29/Oct/23  Resolved: 27/Mar/18

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

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

Issue Links:
Depends
is depended on by SERVER-33523 Add timestamp support to CollectionMe... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-03-12, Sharding 2018-03-26, Sharding 2018-04-09
Participants:

 Description   

This ticket covers the work for making the ChunkManager support routing at different timestamps. Essentially, implementing the CatalogCache::getCollectionRoutingInfoAt interface.

As part of this work, in addition to the existing ChunkManager unit-test coverage, we should add new tests which construct routing information at different points in time and ask for:

  • The latest Timestamp (no Timestamp should be covered by the existing coverage)
  • Timestamps at Timestamp boundaries (making sure we don't have boundary condition bugs)
  • Timestamps, which are before the earliest supported, ensuring that TimestampTooOld exception is thrown


 Comments   
Comment by Githook User [ 27/Mar/18 ]

Author:

{'email': 'martin.neupauer@10gen.com', 'name': 'Martin Neupauer', 'username': 'MartinNeupauer'}

Message: SERVER-33453 - Add timestamp support to the ChunkManager
Branch: master
https://github.com/mongodb/mongo/commit/e6503239af00e7a7a5848ed7784142ac904e4218

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