hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers
Date Fri, 27 Mar 2015 22:12:54 GMT

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

Li Lu commented on YARN-3051:

bq. So when I say get all configs for an app. I do that by specifying fields=configs in REST
URL. And if I want metrics and configs for an app, I can say fields=configs,metrics.

OK, I'm just thinking out loud. 
So do we need to touch both the entity table and the config/metric table on the underlying
storage? Now suppose I've already have a timeline entity, without its metrics, and I'd like
to draw a time series for its hdfs_bytes_write. Do I need to regenerate the timeline entity
together with the metric, or I can say something like "get hdfs_bytes_write for this context"?

BTW, we may want to consider the relationship between the context and timeline entities on
the reader side. The context information is the PK of the timeline entity rows. 

> [Storage abstraction] Create backing storage read interface for ATS readers
> ---------------------------------------------------------------------------
>                 Key: YARN-3051
>                 URL: https://issues.apache.org/jira/browse/YARN-3051
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Varun Saxena
> Per design in YARN-2928, create backing storage read interface that can be implemented
by multiple backing storage implementations.

This message was sent by Atlassian JIRA

View raw message