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

Create new config.placementHistory collection as part of the config server startup routine

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-08-22

    Description

      In order to optimise the connections opened by a mongos process when a nss.watch() request is received, the config server will have to persist in a new collection (called config.placementHistory) historical metadata about which shards of the cluster were hosting one or more chunks of nss at a specific point in time.

      The objectives of this ticket are:

      • The encoding of the schema for config.placementHistory, defined as

        {
        namespace: string, // references db or collection
        timestamp: Timestamp,
        shards: array<ShardId> // may be empty
        }
        

      • The instantiation of config.placementHistory as part of the initialisation of the ShardingCatalogManager (with an index over namespace+timestamp).

      Attachments

        Activity

          People

            paolo.polato@mongodb.com Paolo Polato
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: