Github user jvrao commented on the issue:
https://github.com/apache/bookkeeper/pull/145
On Thu, May 11, 2017 at 8:09 AM Matteo Merli <notificati...@github.com>
wrote:
> @jvrao <https://github.com/jvrao> I agree with the point of separating
> the recovery vs non-recovery.
>
> At yahoo we were using log sniffer to get alerts from all error messages.
> If an error message is not symptom of something wrong that require some
> operator action, then it only adds to noise.
>
> In the specific, since you cannot distinguish, just by seeing this error
> messages, whether something was *really* wrong or everything is ok.. the
> error message is not useful.
>
>
That's exactly my point. Can we use this opportunity to do the right fix
instead of masking real errorcases?
â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/bookkeeper/pull/145#issuecomment-300819767>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAChroDChR08-PSMdZ4oatC0P1N9Brgcks5r4yTGgaJpZM4NXBv9>
> .
>
--
Sent from iPhone
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
