Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-33453

Add timestamp support to the ChunkManager

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.4
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • Sharding 2018-03-12, Sharding 2018-03-26, Sharding 2018-04-09

      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

            Assignee:
            martin.neupauer@mongodb.com Martin Neupauer
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: