[DOCS-12736] Add arbiter/RCM considerations to Replica Set Deployment Architectures Created: 22/May/19  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: James Kovacs Assignee: Unassigned
Resolution: Won't Do Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

Replica Set Deployment Architectures discusses the use of arbiters but does not discuss the considerations noted in Read Concern majority and Three-Member PSA. We should document the WiredTiger cache pressure concerns when using arbiters and Read Concern majority when discussing deployment architectures and link to that documentation.

We should also point out that WiredTiger cache pressure issues can occur with any replica set that includes an arbiter. In a PSSSA you can have cache pressure build if two nodes are down. Although simultaneous node failures are unlikely, it can happen easily during a network partition or data centre outage when the replica set is split between multiple data centres.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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