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.
- depends on
-
SERVER-29637 make shards obtain UUID for sharded collections from config server on setFeatureCompatibilityVersion: 3.6
-
- Closed
-
- is related to
-
SERVER-33714 Downgrading FCV from 3.6 to 3.4 leaves an admin.system.keys collection on shards that on upgrade is orphaned and renamed without a UUID
-
- Closed
-