[
https://issues.apache.org/jira/browse/TEZ-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13981829#comment-13981829
]
Siddharth Seth commented on TEZ-1002:
-------------------------------------
Patch seems to have a conflict with TestHistoryEventsProtoConversion. Also, the
unit tests for TestAMContainer are failing. Other than that the patch looks
good.
[~hitesh], RecoveryParser does check for CONTAINER_LAUNCHED - which is also not
a Recovery Event. Should events like that be removed from the RecorveryParser ?
> No HISTORY event for CONTAINER_STOP_REQUEST
> -------------------------------------------
>
> Key: TEZ-1002
> URL: https://issues.apache.org/jira/browse/TEZ-1002
> Project: Apache Tez
> Issue Type: Sub-task
> Affects Versions: 0.4.0
> Reporter: Gopal V
> Assignee: Gopal V
> Priority: Trivial
> Attachments: TEZ-1002.1.patch, TEZ-1002.2.patch, TEZ-1002.4.patch
>
>
> Tez AM logs have history events for launched containers, but no history
> events for stopped containers.
> This makes it hard to verify the number of containers alive from history
> events.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
