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] [Commented] (YARN-4455) Support fetching metrics by time range
Date Thu, 20 Jul 2017 05:59:00 GMT

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

Vrushali C commented on YARN-4455:

bq. From above discussion I understand that only flow run entity table need to be timestamp
supplemented. Currently, other tables has this behavior where timestamp is supplemented while
storing entities. Could we do it in another JIRA?

I believe this patch is for application and entities timeseries, not for the flow run timeseries.
The application and entity tables do not need supplemented timestamp. Wondering where are
you seeing that these tables have supplemented timestamp? 

For the flow run table, the coprocessor will intercept and return only one metric value per
metric. So we do not need to use the supplemented timestamp in the reader code. That supplemented
timestamp is an internal coprocessor implementation detail, which is not to be used by regular
reader and writer code.  

> Support fetching metrics by time range
> --------------------------------------
>                 Key: YARN-4455
>                 URL: https://issues.apache.org/jira/browse/YARN-4455
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-5355
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>              Labels: YARN-5355, yarn-5355-merge-blocker
>         Attachments: YARN-4455-YARN-5355.01.patch, YARN-4455-YARN-5355.02.patch, YARN-4455-YARN-5355.03.patch

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message