You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org> on 2018/12/30 04:18:01 UTC

[jira] [Updated] (AVRO-1666) avro.ipc.Responder logger is too noisy and have system/user error as WARN

     [ https://issues.apache.org/jira/browse/AVRO-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thiruvalluvan M. G. updated AVRO-1666:
--------------------------------------
    Component/s: java

> 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: Apache Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.7.7
>            Reporter: Jacek Migdal
>            Priority: Major
>   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 avro.icp.Responder:
> 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
(v7.6.3#76005)