[
https://issues.apache.org/jira/browse/FLUME-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685656#comment-16685656
]
Hudson commented on FLUME-3087:
-------------------------------
SUCCESS: Integrated in Jenkins build flume-trunk #732 (See
[https://builds.apache.org/job/flume-trunk/732/])
FLUME-3087 Change log level from WARN to INFO (szaboferee:
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=5cfa8be4174084b41d9b14aaf468da79e7a1ea71])
* (edit) flume-ng-sdk/src/main/java/org/apache/flume/api/NettyAvroRpcClient.java
> Change log level from WARN to INFO when using default "maxIOWorkers" value.
> ---------------------------------------------------------------------------
>
> Key: FLUME-3087
> URL: https://issues.apache.org/jira/browse/FLUME-3087
> Project: Flume
> Issue Type: Wish
> Components: Client SDK
> Affects Versions: 1.7.0
> Reporter: Takafumi Saito
> Priority: Minor
> Fix For: 1.9.0
>
> Attachments: FLUME-3087.patch
>
>
> This message confuse us when looking warn log.
> {noformat}
> WARN 2017-04-21 00:23:38,155 [SinkRunner-PollingRunner-DefaultSinkProcessor]
> org.apache.flume.api.NettyAvroRpcClient:634 - Using default maxIOWorkers
> {noformat}
> When using default value, I think the log level should be set INFO rather
> than WARN.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@flume.apache.org
For additional commands, e-mail: issues-h...@flume.apache.org
