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

Drop admin.system.keys on CSRS downgrade from 3.6 fcv to 3.4 fcv

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc4
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • Sharding 2017-06-19, Sharding 2017-10-23, Sharding 2017-11-13

      The admin.system.keys collection should be dropped on downgrade csrs to v3.4 (dependent on SERVER-29637)

      Here is the scenario we want to prevent:
      1. Upgrade csrs to v3.6.
      2. Downgrade csrs to v3.4.
      3. Either add a new node to csrs or maybe one of the secondaries became too stale and need to do initial sync.
      4. One of the secondary will now claim to be 'replicated' after the sync without copying the keys.
      5. Upgrade csrs to v3.6. One of the secondary will not contain the existing keys even though it is supposed to be 'caught up'.

      Note: this can be an issue because of selective initial sync

      A test should be added to verify this scenario does not happen.

            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            0 Vote for this issue
            3 Start watching this issue