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

need to store upgrade/downgrade in progress for sharding

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.6.0-rc0
    • None
    • Sharding, Storage
    • None
    • Fully Compatible
    • ALL
    • Storage 2017-10-02, Storage 2017-10-23
    • 0

    Description

      For sharding we need to know whether an upgrade or downgrade is in process, so in the setFeatureCompatibilityVersion command, where we set the schema version (featureCompatibility.isSchemaVersion36, we need to majority write a targetVersion field in the feature compatibility document with value "3.4" or "3.6" depending on the target schema version.

      Before successful completion, the targetVersion field must be cleared. Upgrade/downgrade must be idempotent. As the parser for the setFeatureCompatibilityVersion needs to be changed, we should aim to transition it to IDL unless that expands the scope of this ticket too much.

      Attachments

        Activity

          People

            louis.williams@mongodb.com Louis Williams
            geert.bosch@mongodb.com Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: