Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
0.1
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
- links to