Details
-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
1
Description
With commit https://github.com/couchbase/eventing/commit/782d8f580a8e3821e28d129dbfa1a432ca484e67 , in Eventing we enabled loggers for GoCB/gocbcore. I tried simulating rebalance with that patch in-place. I see spam in eventing.log because of it and we could potentially lose important debugging information because of it.
2018-06-20T16:46:27.564+05:30 [Error] memdClient read failure: read tcp 192.168.0.14:54721->192.168.0.14:12002: use of closed network connection
|
2018-06-20T16:46:27.564+05:30 [Error] Failed to shut down client connection (close tcp 192.168.0.14:54721->192.168.0.14:12002: use of closed network connection)
|
2018-06-20T16:46:27.610+05:30 [Error] memdClient read failure: read tcp 192.168.0.14:54723->192.168.0.14:12002: use of closed network connection
|
2018-06-20T16:46:27.610+05:30 [Error] Failed to shut down client connection (close tcp 192.168.0.14:54723->192.168.0.14:12002: use of closed network connection)
|
2018-06-20T16:46:27.655+05:30 [Error] memdClient read failure: read tcp 192.168.0.14:54724->192.168.0.14:12002: use of closed network connection
|
2018-06-20T16:46:27.655+05:30 [Error] Failed to shut down client connection (close tcp 192.168.0.14:54724->192.168.0.14:12002: use of closed network connection)
|
2018-06-20T16:46:29.701+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:29.838+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:29.949+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.055+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.229+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.333+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.492+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.618+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.721+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.731+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.731+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.732+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.859+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.877+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.940+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.964+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:30.979+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.189+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.292+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.439+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.445+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.545+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.548+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.648+05:30 [Warn] Attempted to stop tracing on untraced request
|
2018-06-20T16:46:31.650+05:30 [Warn] Attempted to stop tracing on untraced request
|
Objective of this bug:
- Avoid unnecessary logging at INFO log level for GoCB
- How can tracing be turned off for GoCB?
Attachments
Issue Links
- has to be done before
-
-
- Closed
-