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

voting inMemory nodes should refuse to join replica sets that have writeConcernMajorityJournalDefault set to true

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Replication, Storage
    • ALL

    Description

      As per the docs, you must set writeConcernMajorityJournalDefault to false if you are running voting, but non-journaling, nodes in your replica set:
      https://docs.mongodb.com/manual/reference/replica-configuration/#rsconf.writeConcernMajorityJournalDefault
      If you do not do this, the effect will be that your majority writes may hang if a majority of nodes includes a non-journaling node.
      A worse effect is that if you also use --enableMajorityReadConcern, the commit level will never advance, and so the majority snapshot never advances. This can eventually fill up cache memory with write history.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-29649 Add startupWarning when a replset node is running with --nojournal but hasn't set writeConcernMajorityJournalDefault to false

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-38685 Startup warning if In-Memory SE is used and writeConcernMajorityJournalDefault is true

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: