hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-947) Defining the history data classes for the implementation of the reading/writing interface
Date Mon, 21 Oct 2013 21:01:44 GMT

    [ https://issues.apache.org/jira/browse/YARN-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801067#comment-13801067
] 

Zhijie Shen commented on YARN-947:
----------------------------------

ApplicationAttemptState will make this jira depend on YARN-978 as well, which involves more
work of review? Shall we simplify the work here? Anyway, it's a single field change. If we
finally conclude that ApplicationAttemptState is necessary in YARN-978, it won't be big change
for the history data records.

> 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)

Mime
View raw message