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

Add top-level `onCurrentShardSince` field to `config.chunk` entries

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26
    • 161

      The history field on config.chunks holds an array of objects in the following format:

      {validAfter: Timestamp(12345), shard: "shardName"}

      The auto-merger will be expected to act based on the value of the higher validAfter present in the history, but indexing arrays can be much more inefficient than indexing top-level fields. In order to avoid performance issues, purpose of this ticket is to add the same field also at the top-level.

            Assignee:
            silvia.surroca@mongodb.com Silvia Surroca
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: