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

setProfilingLevel() does not accept zero for slowms parameter

    XMLWordPrintable

    Details

    • 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 }

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: