getCmdLineOpts.parsed showing journal field in wrong place

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.6.0-rc3
    • Affects Version/s: 2.6.0-rc2
    • Component/s: Admin
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I thought that journal:true should now appear as storage.journal.enabled: true?

      queues:SECONDARY> db.runCommand('getCmdLineOpts');
      {
      	"argv" : [
      		"/data/dist/mongodb-linux-x86_64-2.6.0-rc2/bin/mongod",
      		"--config",
      		"/data/mmsdbqueues/conf"
      	],
      	"parsed" : {
      		"config" : "/data/mmsdbqueues/conf",
      		"journal" : true,
      		"logpath" : "/data/mmsdbqueues/run.log",
      		"net" : {
      			"port" : 27800
      		},
      		"processManagement" : {
      			"fork" : true
      		},
      		"replication" : {
      			"replSet" : "queues"
      		},
      		"sharding" : {
      			"shardsvr" : true
      		},
      		"storage" : {
      			"dbPath" : "/data/mmsdbqueues/"
      		},
      		"systemLog" : {
      			"logAppend" : true
      		}
      	},
      	"ok" : 1
      }
      

      The config file:

      cat /data/mmsdbqueues/conf 
      fork=true
      rest=false
      shardsvr=true
      logappend=true
      logpath=/data/mmsdbqueues/run.log
      dbpath=/data/mmsdbqueues/
      journal=true
      port=27800
      replSet=queues
      

              Assignee:
              Shaun Verch (Inactive)
              Reporter:
              Cailin Nelson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: