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

InMemory engine startupwarnings confusing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0, 4.4.2, 4.2.11, 4.0.22
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2, v4.0, v3.6
    • Steps To Reproduce:
      Hide

      Run a mongod process with engine=inMemory and writeConcernMajorityJournalDefaul=true (default value).

      Show
      Run a mongod process with engine=inMemory and writeConcernMajorityJournalDefaul=true (default value).
    • Epic Link:
    • Sprint:
      Execution Team 2020-10-19

      Description

      As a consequence of the changes in SERVER-44796 if you start a mongod with the engine=inMemory you get duplicate startup warnings and the one about the journal may be confusing:

      2020-02-05T18:07:30.855+0000 I REPL     [conn36] ** WARNING: This replica set node is running without journaling enabled but the
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          writeConcernMajorityJournalDefault option to the replica set config
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          is set to true. The writeConcernMajorityJournalDefault
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          option to the replica set config must be set to false
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          or w:majority write concerns will never complete.
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          In addition, this node's memory consumption may increase until all
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          available free RAM is exhausted.
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36]
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36]
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] ** WARNING: This replica set node is using in-memory (ephemeral) storage with the
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          writeConcernMajorityJournalDefault option to the replica set config
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          set to true. The writeConcernMajorityJournalDefault option to the
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          replica set config must be set to false
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          or w:majority write concerns will never complete.
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          In addition, this node's memory consumption may increase until all
      		 
      2020-02-05T18:07:30.855+0000 I REPL     [conn36] **          available free RAM is exhausted.

      Can we suppress the first warning shown in my example when using engine=inMemory to avoid confusion?

      Thanks.

        Attachments

          Issue Links

          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-44796 Adjust nojournal startup warning to be more compelling

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

            Activity

              People

              Assignee:
              gregory.noma Gregory Noma
              Reporter:
              emilio.scalise Emilio Scalise
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: