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

--profile option doesn't create the system.profile collection if it doesn't already exist

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 2.0.4
    • Admin, Performance
    • None
    • ALL

    Description

      If you start mongod with --profile to enable profiling, nothing will actually be recorded because the system.profile collection doesn't exist. You can then either manually create system.profile with the createCollection command, or you can setProfilingLevel to 0 then back to the level you want (which will create system.profile for you).

      Attachments

        Activity

          People

            Unassigned Unassigned
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: