[
https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327604#comment-14327604
]
Devaraj K commented on YARN-3197:
---------------------------------
I am not completely convinced to change the log level to debug, even if there
are many logs those would be one log per container. If we change the log level
to debug then we would be missing the update of those containers after NM
restart in the usual cases where the log level is Info. And also there is a
debug log in the caller method would probably serve the same and (rmContainer
== null) {} log wouldn't be required if you have decided to make the log level
as debug.
{code:xml}
LOG.debug("Container FINISHED: " + containerId);
{code}
IMO, we don't need to explicitly derive and print the application id from
container id, just logging container id would be enough and user can derive
application id from it if they really want.
> 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)
