[DOCS-13611] Investigate changes in SERVER-45091: Support arbiters on safe reconfig and add tests Created: 23/Apr/20  Updated: 13/Nov/23  Resolved: 26/Jun/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.4, 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: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: docs-replication
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-45091 Support arbiters on safe reconfig and... Closed
Participants:
Days since reply: 3 years, 32 weeks, 5 days ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

Arbiters persist the config to disk the same as other members and propagate it. In a PSA set with the secondary down, the set can still complete a reconfig if the arbiter is a quorum member.

Description of Linked Ticket

Done Arbiters must follow the same voting rules as data nodes regarding configTerm and configVersion. Add unittests in topology_coordinator_v1_test.cpp.

Done Ensure we have tests that add/remove arbiters with non-force replSetReconfig. (Done in SERVER-46218.)

Done Test that an arbiter gossips the config to other nodes including configTerm.

Done Count arbiters as quorum members for Config Replication. Depends on SERVER-45085. Test: A PSA set with the secondary down can acknowledge replSetReconfig.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 26/Jun/20 ]

Author:

{'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com', 'username': 'rkumar-mongo'}

Message: DOCS-13611: Clarifying voting majorities for replica set reconfig
Branch: master
https://github.com/mongodb/docs/commit/b1f5f8c090c38ff6c4a6c7703667db13d4ad5993

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