You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flume.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/11/13 16:45:00 UTC
[jira] [Commented] (FLUME-3087) Change log level from WARN to INFO
when using default "maxIOWorkers" value.
[ https://issues.apache.org/jira/browse/FLUME-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16685460#comment-16685460 ]
ASF subversion and git services commented on FLUME-3087:
--------------------------------------------------------
Commit 5cfa8be4174084b41d9b14aaf468da79e7a1ea71 in flume's branch refs/heads/trunk from [~fszabo]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=5cfa8be ]
FLUME-3087 Change log level from WARN to INFO
when using default "maxIOWorkers" value.
Reviewers: Denes Arvay, Ferenc Szabo
(Takafumi Saito via Ferenc Szabo)
> 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-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org