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

getParameter for journalCommitInterval returns 0

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • 4.1.11
    • Affects Version/s: 2.6.0-rc0
    • Component/s: Admin
    • Fully Compatible
    • ALL
    • Hide

      1) start mongod without setting journalCommitInterval in the config file
      2) run getParameter
      3) add journalCommitInterval to the config file
      4) run getParameter

      Show
      1) start mongod without setting journalCommitInterval in the config file 2) run getParameter 3) add journalCommitInterval to the config file 4) run getParameter
    • Storage NYC 2019-05-20

      Per http://docs.mongodb.org/manual/reference/configuration-options the default value for journalCommitInterval is 100 or 30. Starting mongod from 2.6 RC0 using the MacOS binary (or something I build myself) I get 0 when it is not set in the config file.

      > db.adminCommand({getParameter:1, journalCommitInterval:1})
      { "journalCommitInterval" : 0, "ok" : 1 }
      

      When I explicitly set journalCommitInterval to 200 in the config file I get 200

      > db.adminCommand({getParameter:1, journalCommitInterval:1})
      { "journalCommitInterval" : 200, "ok" : 1 }
      

      This is confusing because a non-zero value really is being used given this code in dur.cpp

                      unsigned ms = storageGlobalParams.journalCommitInterval;
                      if( ms == 0 ) { 
                          // use default
                          ms = samePartition ? 100 : 30;
                      }
      

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            mdcallag Mark Callaghan
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: