[
https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326980#comment-14326980
]
Rohith commented on YARN-3197:
------------------------------
bq. I think INFO could be fine since it will be at most once for each container.
I agree this log message is most once for each containers But IIUC, the above
log message would not help to analyze any issue in cluster rather it is just
only information. This would come because NodeManger may be delayed in
identifying container has finished and sending its status.
Consider NM restart , NM recovers all the containers and sends all the
container status(running and completed) while registering. But application
already would have completed and scheduler prints above message which is not
really required. It just fills log files.
May be above scenario can be considered for changing log level to DEBUG.
> Confusing log generated by CapacityScheduler
> --------------------------------------------
>
> Key: YARN-3197
> URL: https://issues.apache.org/jira/browse/YARN-3197
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.6.0
> Reporter: Hitesh Shah
> Assignee: Varun Saxena
> Priority: Minor
> Attachments: YARN-3197.001.patch
>
>
> 2015-02-12 20:35:39,968 INFO capacity.CapacityScheduler
> (CapacityScheduler.java:completedContainer(1190)) - Null container
> completed...
> 2015-02-12 20:35:39,968 INFO capacity.CapacityScheduler
> (CapacityScheduler.java:completedContainer(1190)) - Null container
> completed...
> 2015-02-12 20:35:39,968 INFO capacity.CapacityScheduler
> (CapacityScheduler.java:completedContainer(1190)) - Null container
> completed...
> 2015-02-12 20:35:40,960 INFO capacity.CapacityScheduler
> (CapacityScheduler.java:completedContainer(1190)) - Null container
> completed...
> 2015-02-12 20:35:40,960 INFO capacity.CapacityScheduler
> (CapacityScheduler.java:completedContainer(1190)) - Null container
> completed...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
