You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2016/10/27 19:42:58 UTC

[jira] [Commented] (YARN-3821) Scheduler spams log with messages at INFO level

    [ https://issues.apache.org/jira/browse/YARN-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612973#comment-15612973 ] 

Karthik Kambatla commented on YARN-3821:
----------------------------------------

Over the last year, I haven't seen cases where these log messages have added any information. 

Some of these log messages have been removed or relegated to a lower level. I am in favor of lowering the log level of the remaining.

> Scheduler spams log with messages at INFO level
> -----------------------------------------------
>
>                 Key: YARN-3821
>                 URL: https://issues.apache.org/jira/browse/YARN-3821
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler, fairscheduler
>    Affects Versions: 2.8.0
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Minor
>              Labels: oct16-easy
>         Attachments: YARN-3821.patch
>
>
> The schedulers spams the logs with messages that are not providing any actionable information. There is no action taken in the code and there is nothing that needs to be done from an administrative point of view. 
> Even after the improvements for the messages from YARN-3197 and YARN-3495 administrators get confused and ask what needs to be done to prevent the log spam.
> Moving the messages to a debug log level makes far more sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org