mongod incorrectly allows config servers to be started without journaling if specified in the config file

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Config servers require journaling to be on to support committed reads. If you try to specify --nojournal with --configsvr on the command line, we correctly error. If, however, you specify storage.journal.enabled:false in a config file along with sharing.clusterRole:configsvr, we allow it. This can cause all majority reads against the config servers to fail, rendering the cluster unusable.

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: