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

Docs for SERVER-30347: Fail startup when running wiredTiger with --nojournal as part of a replica set

    XMLWordPrintable

    Details

      Description

      Documentation Request Summary:

      If it isn't clear from the ticket description, this ticket disallows --nojournal in the specific case of running WT on a replica set node.

      Engineering Ticket Description:

      Running WT without journaling will no longer be a supported configuration for a replica set node in 3.6.

      Scope of changes:

      • relnotes
        • 4.0
        • 3.6-compat
        • 4.0-compat
      • nojournal
        • source/includes/extracts-manage-journaling.yaml
        • source/includes/options-mongod.yaml
        • source/includes/wiredtiger-node-nojournal.rst
      • storage.journal
        • source/includes/options-mongod.yaml
        • source/administration/production-notes.txt
        • source/includes/options-conf.yaml
        • source/core/wiredtiger.txt
        • source/reference/connection-string.txt
      • writeCOncernmajorityJournalDefault
        • source/core/inmemory.txt
        • source/core/journaling.txt
        • source/includes/extracts-concurrency-consistency-recency.yaml
        • source/includes/options-conf.yaml
        • source/includes/options-mongod.yaml
        • source/reference/replica-configuration

      Impact to other docs outside of this product:

      none (per Marian search – journaling from OpsMgr/Cloud mgr point back to manual)

      MVP:

      Resources:

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              kay.kim Kay Kim (Inactive)
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                3 years, 19 weeks, 2 days ago
                Date of 1st Reply: