[
https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735572#comment-13735572
]
Zhijie Shen commented on YARN-978:
----------------------------------
I'm not pretty sure how users would make use of the attempt information, but I
think it does no harm to expose the attempt information listed in the patch,
which on the other side, give users more options.
Compared with application report, the duplicated fields:
* diagnostics
* finalApplicationStatus
* host
* rpcPort
* trackingUrl
However, the fields in an application report, is extracted from the *current*
attempt. Therefore, through the application report, users can only know this
information of the current attempt. In the case of application history, the
information should belong to that of the last attempt when the application is
finished.
In contrast, an application may have launched several attempts before it is
finished. The aforementioned information of each attempt may be different.
Therefore, this information should not be duplicate.
bq. For a non-running attempt, what is the tracker url and the original
tracking url?
hm... Do you mean the tracking url only work for a running attempt?
bq. Failed attempts have a failed yarn state. Failed attempts would register an
app state with the RM ( during unregister ) if that attempt is the final attempt
Sorry, I mean all attempts should have a finalApplicationStatus, shouldn't they?
> [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation
> ----------------------------------------------------------------------
>
> Key: YARN-978
> URL: https://issues.apache.org/jira/browse/YARN-978
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Mayank Bansal
> Assignee: Xuan Gong
> Fix For: YARN-321
>
> Attachments: YARN-978-1.patch, YARN-978.2.patch, YARN-978.3.patch
>
>
> We dont have ApplicationAttemptReport and Protobuf implementation.
> Adding that.
> Thanks,
> Mayank
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
