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

Update --enableMajorityReadConcern section

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • Affects Version/s: None
    • Component/s: Server
    • Labels:
      None

      ----------------------------

      Original Description

      Documentation and code contradict each other on `--enableMajorityReadConcern`.
      Documentation says that in v3.6 majority read concern is always enabled, and that the switch has no effect (https://docs.mongodb.com/v3.6/reference/program/mongod/#cmdoption-mongod-enablemajorityreadconcern)
      However, according to https://jira.mongodb.org/browse/SERVER-32022, the switch is re-enabled in v3.6.1.
      ----------------------------

      Description

      Scope of changes (files that need work and how much)

      Impact to other docs outside of this product

      MVP (work and date?)

      Resources (e.g. Scope Docs, Invision)

            Assignee:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Reporter:
            josef.ahmad@mongodb.com Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              5 years, 29 weeks ago