hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vrushali C (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3031) create backing storage write interface for ATS writers
Date Mon, 09 Feb 2015 20:04:35 GMT

     [ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vrushali C updated YARN-3031:
    Attachment: YARN-3031.01.patch

Attaching the first draft of the interface. The patch will not compile presently since this
code depends on the TimelineServiceEntity class that's being added as part of  https://issues.apache.org/jira/browse/YARN-3041
(create the ATS entity/event API).

The interface calls out two main functionalities:  single entity writes and aggregations.

Since several read APIs would depend on data being available at the aggregated level, it needs
to be called out in the interface so that any writer class implementing this interface takes
into consideration entity aggregation functionality. 

The aggregate functionality may be implemented by writer class implementations in a way that
is optimal to that storage. For instance, hbase may choose to have co-processors do the aggregation;
then that writer implementation code would have the aggregate function as a no-op. 

> create backing storage write interface for ATS writers
> ------------------------------------------------------
>                 Key: YARN-3031
>                 URL: https://issues.apache.org/jira/browse/YARN-3031
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Vrushali C
>         Attachments: YARN-3031.01.patch
> Per design in YARN-2928, come up with the interface for the ATS writer to write to various
backing storages. The interface should be created to capture the right level of abstractions
so that it will enable all backing storage implementations to implement it efficiently.

This message was sent by Atlassian JIRA

View raw message