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

Profiler setting of low "slowms" creates huge log file

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • None
    • None
    • None
    • None
    • ALL

    Description

      When updating the profiler settings to log queries profiling info into the collection system.profile, the mongod.log file is recording every query in the text file.

       

      This leads to filling the hard drive very fast, for nothing. I already have all the information in the collection, that i can query using filters.

       

      I am forced to disable the profiling or to set the slowQuery threshold to a high value, otherwise the hard drive will be full very fast because of mongod.log. The settings of the mongod.log profiling and the settings of system.profile profiling should not be the same setting. It's not the same thing. The system.profile is a rotating log that can never fill the hard drive.

       

      The system.profile collection can be used even with fast queries, to determine the query plans and search coll scans, in memory sorts, and bad indexes. Even if the query is super fast with a small data sample.

       

      It seems impossible to use as it is. I have disabled it, though i need profiling, but without filling the hard drive with mongod.log detailed query logs.

       

      Regards.

      Attachments

        Issue Links

          Activity

            People

              yuan.fang@mongodb.com Yuan Fang
              bonjourjoel@gmail.com Joel J
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: