hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6389) [ATSv2] metricslimit query parameter do not work
Date Fri, 24 Mar 2017 19:17:41 GMT

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

Rohith Sharma K S commented on YARN-6389:

Btw, I am using hbase-1.1.5. But the same hbase version is used in old build where metricslimit
is working fine. 
And also I looked into tests modifying a bit. But it appears in test {{metricslimit}} is working

> [ATSv2] metricslimit query parameter do not work
> ------------------------------------------------
>                 Key: YARN-6389
>                 URL: https://issues.apache.org/jira/browse/YARN-6389
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelinereader
>            Reporter: Rohith Sharma K S
>            Assignee: Varun Saxena
>            Priority: Critical
> It is observed that metricslimit query parameter do not work. And also by default metricslimit
is set to 1, all the metrics versions are retrieved. 
> One thing I noticed that even though GenericEntityReader is setting Scan.setMaxVersions(),
all the metrics are retrieved. It appears something wrong in TimelieneWritter or the way hbase
filters is being used. 

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