[
https://issues.apache.org/jira/browse/TEZ-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254320#comment-14254320
]
Bikas Saha commented on TEZ-287:
--------------------------------
Not done. Its only present in the history events.
> Pass terminationCause information back to client-side (access via
> DAGClient.ApplicationReport)
> ----------------------------------------------------------------------------------------------
>
> Key: TEZ-287
> URL: https://issues.apache.org/jira/browse/TEZ-287
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Mike Liddell
> Attachments: TEZ-287.1.patch
>
>
> need to determine how much to send:
> - dag termination cause
> - vertex termination cause
> - all tasks termination cause
> Perhaps logic such as
> - dont send task termination cause (too much volume with high noise ratio)
> - however, any Vertex with VertexTerminationCause=OWN_TASK_FAILURE could
> failingTaskCount and a single failed-task-ID to aid post-mortem. (it is
> probably interesting to user if few task of many failed vs all tasks failed.
> when there are few failing tasks, it might be helpful to have an ID on hand
> to start the diagnosis)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
