[SERVER-29653] Drop admin.system.keys on CSRS downgrade from 3.6 fcv to 3.4 fcv Created: 15/Jun/17  Updated: 30/Oct/23  Resolved: 07/Nov/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.0-rc4

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-221
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29637 make shards obtain UUID for sharded c... Closed
Related
is related to SERVER-33714 Downgrading FCV from 3.6 to 3.4 leave... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-06-19, Sharding 2017-10-23, Sharding 2017-11-13
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 07/Nov/17 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-29653 Drop admin.system.keys on CSRS downgrade from 3.6 fcv to 3.4 fcv
Branch: master
https://github.com/mongodb/mongo/commit/82448e638f736c505cf5caccbbefe058cddcf15f

Generated at Thu Feb 08 04:21:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.