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

Startup warning if In-Memory SE is used and writeConcernMajorityJournalDefault is true

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • v4.0, v3.6
    • Repl 2019-06-03, Repl 2019-06-17

    Description

      We should a startup warning if a node is using the In-Memory storage engine but has also enabled writeConcernMajorityJournalDefault. Per the documentation, that option is unsupported in replica sets that contain In-Memory nodes and can cause problems if not set to false.

      Attachments

        Issue Links

          is documented by

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

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35786 lastDurable optime should be updated after batch application on non-durable storage engines

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31158 voting inMemory nodes should refuse to join replica sets that have writeConcernMajorityJournalDefault set to true

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-38441 In-Memory pins all dirty data in cache because of read concern majority

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

          Activity

            People

              vishnu.kaushik@mongodb.com Vishnu Kaushik
              daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: