Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12736

Add arbiter/RCM considerations to Replica Set Deployment Architectures

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • None
    • manual, Server
    • None

    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.)

      Attachments

        Activity

          People

            Unassigned Unassigned
            james.kovacs@mongodb.com James Kovacs
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              1 year, 14 weeks, 2 days ago