hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4455) Support fetching metrics by time range
Date Wed, 22 Mar 2017 18:03:41 GMT

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

Varun Saxena commented on YARN-4455:

Thanks [~vrushalic] for the comments.

bq. If we know the metric name, we should set it in the scan and then use HBase scan#setTimeRange

If we use setTimeRange or setTimestamp wouldn't it apply to all columns? I mean if created
time column has a timestamp which does not fall within range, wouldn't that be excluded? IIUC,
all cells have a timestamp.

bq. We should ensure we limit the number of records being returned. We should also set the
maxVersions to be 1.
Yes we currently have a metricsLimit query param which by default is 1. And we use it to set
max versions as you have suggested above.

> 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-2928
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>              Labels: YARN-5355, yarn-5355-merge-blocker

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