[
https://issues.apache.org/jira/browse/YARN-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329451#comment-14329451
]
Varun Saxena commented on YARN-3197:
------------------------------------
[~leftnoteasy],
Thought so initially but that was making log too verbose. Maybe can do that to
avoid confusion.
Moreover, I think there should be some differentiation between the log where
container is null and the one where application is null.
I think we can say
"Container xxx completed with state yyy but was not found in alive containers
map"
Thoughts ?
Any need to mention the application ID ? That can be derived from container ID.
Right ?
Other log I will change as you suggested.
> 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, YARN-3197.002.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)
