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

Upgrade/downgrade the chunks history on FCV change

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.7.4
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2018-04-09, Sharding 2018-04-23

    Description

      This ticket covers the upgrade/downgrade work in the design spec. It should include writing the history on upgrade and deleting it on downgrade, plus synchronizing the FCV change with any concurrently running move/split/merge operations. It is acceptable to block these operations while the upgrade/downgrade is running, but ideally that blocking should be limited on a per-collection basis and not globally.

      As part of this ticket we should also make the shards and config server reject atClusterTime requests under FCV 3.6 and also that the ChunkManager::getCollectionRoutingInfoAt call will fail if it contains no history.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: