Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-10586

Enabling profiler causes restart, but the ops manager manual does not mention that

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Ops Manager
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      0.1
    • Sprint:
      KANBAN BUCKET

      Description

      Customer found that the mongod process was restarted after he enabled the profiler. This is an expected behaviour. Actually, any mongod configuration change results in a restart. However, it is not documented. Can we add a note of this somewhere in the Ops Manager document?

      Thanks,
      Lungang

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rob.justice Robert Justice (Inactive)
              Reporter:
              lungang.fang Lungang Fang
              Participants:
              Last commenter:
              Robert Justice Robert Justice (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                3 years, 19 weeks, 1 day ago
                Date of 1st Reply: