[SERVER-11125] setProfilingLevel() does not accept zero for slowms parameter - MongoDB Jira

XML

Word

Printable

JSON

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Steps To Reproduce:

Hide

Start up mongod with default profiling values.
At shell, run the following commands
> db.setProfilingLevel(1, 0)
{ "was" : 0, "slowms" : 100, "ok" : 1 }
> db.getProfilingStatus()
{ "was" : 1, "slowms" : 100 }
The result from db.getProfilingStatus() should be
{ "was" : 1, "slowms" : 0 }

Show
Start up mongod with default profiling values. At shell, run the following commands > db.setProfilingLevel(1, 0) { "was" : 0, "slowms" : 100, "ok" : 1 } > db.getProfilingStatus() { "was" : 1, "slowms" : 100 } The result from db.getProfilingStatus() should be { "was" : 1, "slowms" : 0 }

mongod accepts --slowms=0 but the shell command db.setProfiliingLevel(level, slowms) does not. Can we fix the shell command to support slowms=0?

Also, are negative values supported for slowms? This would allow the server to log all queries.

is related to

SERVER-4785 slowms should be per database for profiler

SERVER-457 configure "slow" for query log

related to

SERVER-5266 Make a clearer API for configuring global slowms