avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1666) avro.ipc.Responder logger is too noisy and have system/user error as WARN
Date Fri, 01 May 2015 16:56:06 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523442#comment-14523442

Doug Cutting commented on AVRO-1666:

Moving "system error" to ERROR level seems reasonable.

We might also or instead change the "user error" logging so that the error message alone is
printed at WARN and the stack trace only at INFO.

> avro.ipc.Responder logger is too noisy and have system/user error as WARN
> -------------------------------------------------------------------------
>                 Key: AVRO-1666
>                 URL: https://issues.apache.org/jira/browse/AVRO-1666
>             Project: Avro
>          Issue Type: Bug
>    Affects Versions: 1.7.7
>            Reporter: Jacek Migdal
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> I used avro ipc a lot and enjoy it. Great work! Would love to contribute back.
> We sometimes use avro-ipc exceptions to signal rare, but correct situations (e.g. user
session has ended). Because of the scale this cause tons of WARN logs with stack traces from
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.avro/avro-ipc/1.7.5/org/apache/avro/ipc/Responder.java#156
> Though would like to exclude in log4j, I can't because I'm interested in "system error"
which signal real bug and are also on WARN level.
> Potential solutions that would make me happy:
> 1. Move "user error" to INFO level.
> 2. Move "system error" to ERROR level.
> 3. Have some option/flag to switch of INFO level.
> Happy to write a patch for that, once I get blessing from core developer.

This message was sent by Atlassian JIRA

View raw message