[
https://issues.apache.org/jira/browse/YARN-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhijie Shen updated YARN-934:
-----------------------------
Attachment: YARN-934.4.patch
Talked to [~vinodkv], and we thought it's better to split the each writing
operations into two. One is executed when the object (RMApp, RMAppAttempt or
RMContainer) is started, recording the information that is already available.
The other is executed when the object reaches its finishing stage, recording
the information that is finally determined.
I uploaded a new incremental patch to draft the new writer interface. In
addition to that, I modified ApplicationHistoryStore as well. I change it from
the interface to the abstract class, which extends AbstractService. Therefore,
The implementations of it (e.g. FS storage, DB storage) can make use of the
life cycle of a service, doing the necessary initialization and cleanup work in
the corresponding stage.
> HistoryStorage writer interface for Application History Server
> --------------------------------------------------------------
>
> Key: YARN-934
> URL: https://issues.apache.org/jira/browse/YARN-934
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Zhijie Shen
> Fix For: YARN-321
>
> Attachments: YARN-934.1.patch, YARN-934.2.patch, YARN-934.3.patch,
> YARN-934.4.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
