Karthik Kambatla commented on YARN-3821:

All these are cases when the app, attempt, container are null. We need to get 
to the bottom of why we land in these cases, and handle them appropriately. Out 
of sight, out of mind. I would say let us leave them as is. Or, if people feel 
strongly about turning these logs off, at least file JIRAs for each individual 
case to be investigated. 

> 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
>         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

Reply via email to