[
https://issues.apache.org/jira/browse/YARN-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802013#comment-13802013
]
Zhijie Shen commented on YARN-947:
----------------------------------
bq. BTW yarnapplicationattemptstate is already part of YARN-978.
Yes, I know that. [~jeffgx619], are you fine if I takes
YarnApplicationAttemptState part from your patch of YARN-978? This is because
we want the branch is always compilable.
bq. I think we should use the same states In AHS as we have in RM and we don't
think we should use others states then RM states as thats what we show users to
RM UI/CLI to avoid confusion.
It's not the other states. Actually web UI and CLI is showing
YarnApplicationState instead or RMAppState, as YarnApplicationState is a user
oriented object (it is a proto). That's why we propose
YarnApplicationAttemptState in YARN-978, and we also need YarnContainerState as
well.
> Defining the history data classes for the implementation of the
> reading/writing interface
> -----------------------------------------------------------------------------------------
>
> Key: YARN-947
> URL: https://issues.apache.org/jira/browse/YARN-947
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Fix For: YARN-321
>
> Attachments: YARN-947.1.patch, YARN-947.2.patch, YARN-947.3.patch,
> YARN-947.4.patch, YARN-947.5.patch
>
>
> We need to define the history data classes have the exact fields to be
> stored. Therefore, all the implementations don't need to have the duplicate
> logic to exact the required information from RMApp, RMAppAttempt and
> RMContainer.
> We use protobuf to define these classes, such that they can be ser/des
> to/from bytes, which are easier for persistence.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
