[SERVER-74282] Require all internal server data cleanup be completed before allowing transition to upgraded for replica sets Created: 22/Feb/23  Updated: 29/Oct/23  Resolved: 14/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Huayu Ouyang Assignee: Huayu Ouyang
Resolution: Fixed Votes: 0
Labels: milestone-1, pm-2974-required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-64917 Enable featureFlagDowngradingToUpgrading Closed
is depended on by SERVER-73778 Require all internal server data clea... Closed
Documented
is documented by DOCS-15967 [Server] All internal server data cle... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-03-06, Repl 2023-03-20
Participants:

 Description   

Same as SERVER-73778, but for replica sets.

Before the replica set starts the internal data cleanup step, it should persist a isCleaningServerMetadata : true field to the FCV document, and then remove this when transitioning to downgraded.

We should also check at the beginning of FCV upgrade for this field and fail the upgrade if it exists.

For testing, we should make sure to test that if we fail with either a retryable error or ManualInterventionRequired during internal metadata cleanup, we fail to transition to upgrading.

When entering the CleaningServerMetadata phase we should add a log similar to the ones added in SERVER-67443 and file an Atlas log ingestion request for it



 Comments   
Comment by Githook User [ 14/Mar/23 ]

Author:

{'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}

Message: SERVER-74282 Require all internal server data cleanup be completed before allowing transition to upgraded for replica sets
Branch: master
https://github.com/mongodb/mongo/commit/5a72d04c956573b5e1d293cde526df1018ddfa0e

Generated at Thu Feb 08 06:27:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.