[
https://issues.apache.org/jira/browse/TEZ-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976413#comment-13976413
]
Siddharth Seth commented on TEZ-1002:
-------------------------------------
I think AMContainer would be a better place to generate these events. That has
far more information about the containers, and additional meta-data could be
added to this event at a later point.
Doing this in TaskSchedulerEventHandler increases the possibilities of
generating duplicate events. One case, however, will need to stay - the case in
which an AMContainer hasn't yet been created - which happens when nothing runs
on an allocated container. That container will have an end events without a
start event.
The RecoveryParser also needs to handle the new event type.
> 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 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)
