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

Fix calculation of latest shard placement version change timestamp

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • 7.1.0-rc0, 7.0.0-rc6
    • None
    • None
    • Sharding EMEA
    • ALL

    Description

      In SERVER-77506  we introduced CollectionMetadata::getShardMaxValidAfter() that should return the timestamp of the latest data placement change for this shard.

      Currently, this timestamp is calculated as the maximum validAfter of all chunks currently owned by the given shard. This value does not represent the latest data placement change for the shard because it does not account for the last chunk donated by the shard.

      In fact the timestamp of the latest donated chunk is registered on the chunk itself that after the migration commit is not part anymore of the set of owned chunk by the donor shard.

      Attachments

        Activity

          People

            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: