Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42573

Only warn about readConcernMajority enabled in primary-secondary-arbiter configuration

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.17, 4.3.1, 4.2.3, 4.0.16
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • v4.2, v4.0, v3.6
    • Repl 2019-09-09


      The startup warning about "Read Concern Majority" is shown when the users have an arbiter, regardless of the number of nodes. If we check the documentation, it is only recommended when the replica set is PSA.

      "If you are using a deployment other than a 3-member PSA, you do not need to disable read concern majority."

      When the warning was created on SERVER-37557 it was decided to alert when an arbiter was present, regardless on the replica set configuration:

      "the risk exists in any set with an arbiter, since they allow you to accept writes when the majority commit point cannot move forward. We are going to recommend all sets with arbiters use enableMajorityReadConcern:"false"."

      So, the warning is not following the documentation, and this could be confusing to the MongoDB users.


            xuerui.fa@mongodb.com Xuerui Fa
            miguel.nieto@mongodb.com Miguel Angel Nieto
            0 Vote for this issue
            18 Start watching this issue