[DOCS-13408] Investigate changes in SERVER-46089: Arbiters don't remove configTerm on downgrade Created: 12/Feb/20  Updated: 13/Nov/23  Resolved: 19/Mar/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0, 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: Unassigned
Resolution: Gone away Votes: 0
Labels: docs-replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-13482 Investigate changes in SERVER-46288: ... Closed
Participants:
Days since reply: 3 years, 48 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

4.4 downgrade of arbiter should delete the arbiter data directory as we did for 4.2 downgrade.
https://docs.mongodb.com/manual/release-notes/4.2-downgrade-replica-set/#downgrade-arbiter-replica-set-member-if-any

Description of Linked Ticket

Arbiters don't track FCV so they won't remove the configTerm from their on disk ReplSetConfig object on downgrade. This causes a 4.2 node to fail parsing of the config on restart after binary downgrade.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by A. Jesse Jiryu Davis [ 10/Mar/20 ]

Nevermind, we don't think there are Docs changes needed for this ticket after all. We changed our design so that arbiters have no special upgrade/downgrade requirements that are new in 4.4.

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