[DOCS-15967] [Server] All internal server data cleanup must be completed before replica set upgrade Created: 20/Mar/23  Updated: 13/Nov/23  Resolved: 02/Aug/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 7.0.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kanchana Sekhar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-74282 Require all internal server data clea... Closed
Participants:
Days since reply: 27 weeks, 2 days ago
Story Points: 1

 Description   
Original Downstream Change Summary

If a downgrade previously failed and the cluster is still in a transitionary FCV state, we will not allow upgrading the cluster if cleaning up internal metadata was started but not completed.

Description of Linked Ticket

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 Kanchana Sekhar [ 31/Jul/23 ]

PR: https://github.com/10gen/docs-mongodb-internal/pull/4205

Generated at Thu Feb 08 08:14:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.