We need to clean up our log messages. We generate a lot of noise because many log messages are not actionable, and don't mean anything – they appear to have been put in for original development and debugging, and left there. One example I get asked about a lot is the warning about being unable to release a recursive lock from a mapreduce.
- is duplicated by
-
SERVER-5092 Better named logging with tracing
- Closed
- is related to
-
SERVER-13922 remove dbtemprelease
- Closed
-
SERVER-3989 Cannot suppress ClientCursor::yield "warnings" from logs
- Closed
- related to
-
SERVER-4780 Improve Memory Leak Warning Message
- Closed