[
https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733846#comment-13733846
]
Hitesh Shah commented on YARN-978:
----------------------------------
Let me clarify my concerns.
What attributes' values are different from the overall app vs the attempt? Why
is there a final application status for an attempt when the attribute itself is
described as the status of the application i.e. not the status of an attempt.
For a non-running attempt, what is the tracker url and the original tracking
url? The tracker url today for all application attempts is hidden by a proxy
using a single url. Is the intent now to change this behavior to now have
different proxy urls per attempt?
Failed attempts have a failed yarn state - I am not sure why they would have an
application state. Failed attempts would register an app state with the RM (
during unregister ) if that attempt is the final attempt.
The complete information on all attempts is useful except when it becomes
confusing to users as to what is specific to an attempt. It seems like the
driving use case for this is the application history server and to some extent,
exposing users to the yarn state for the attempt so that they can infer what is
the current state of an attempt ( running/completed/failed ). It would seem
that not replicating data is beneficial to the history server to reduce amount
of duplicated data being stored.
> [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
