[
https://issues.apache.org/jira/browse/TEZ-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500155#comment-14500155
]
Hitesh Shah commented on TEZ-2331:
----------------------------------
[~lichangleo] I think the main scenario for container stopped/released is
usually when the dag is running. If the container stopped info does not show at
the end of an application, that should be ok as a quick check against whether
the application is running or not will let the UI or any consumer of the data
know that the container was stopped when the app completed.
For the most part, given that YARN is already publishing information to ATS on
when a container was started/completed, this info in Tez is not really needed.
The missing piece is that there is currently no way to link the ATS entity to
the YARN container entity.
Due to ATS slowness today, the AM already ends up waiting quite a bit of time
to flush events. Adding more sleep time might not be beneficial given the above
considerations with respect to container stop.
Let me know if this makes sense or if you have any concerns/doubts.
> Container Stop Info Always Missing When Container Reuse Enabled
> ---------------------------------------------------------------
>
> Key: TEZ-2331
> URL: https://issues.apache.org/jira/browse/TEZ-2331
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Chang Li
>
> Inside otherinfo the container's exit status and end time is always missing
> when container reuse is enabled.
> {code}
> {
> "events": [
> {
> "timestamp": 1429225237529,
> "eventtype": "CONTAINER_LAUNCHED",
> "eventinfo": { }
> }
> ],
> "entitytype": "TEZ_CONTAINER_ID",
> "entity": "tez_container_e08_1427829803708_21518_01_000002",
> "starttime": 1429225237529,
> "domain": "Tez_ATS_application_1427829803708_21518",
> "relatedentities": { },
> "primaryfilters": {
> "applicationId": [
> "application_1427829803708_21518"
> ]
> },
> "otherinfo": {
> "containerId": "container_e08_1427829803708_21518_01_000002"
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
