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 Mon, 03 Apr 2017 11:24:41 GMT

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

Rohith Sharma K S commented on YARN-6389:
-----------------------------------------

I verified in HBase-1.2.5, still the same issue. I took help from HBase committers and found
a difference behavior with HBase-1.2.5. Tried from HBase Shell to create simple table and
added 2 versions of values. And the result is surprising. In the below code snippet, scanning
of table with maxversion is not working if we set max_version during create table. This seems
to be an issue from HBase.
{code}
create 't1', {NAME => 'f1', VERSIONS => 100}
put 't2','row','f1:c','value',10000
put 't1','row','f1:c','value2',100111
hbase(main):005:0> scan 't1'
ROW                                           COLUMN+CELL
 row                                          column=f1:c, timestamp=100111, value=value2
 row                                          column=f1:c, timestamp=10000, value=value
1 row(s) in 0.0260 seconds

hbase(main):007:0> scan 't1', { VERSIONS => 1}
ROW                                           COLUMN+CELL
 row                                          column=f1:c, timestamp=100111, value=value2
 row                                          column=f1:c, timestamp=10000, value=value
1 row(s) in 0.0060 seconds
{code}

But one doubt is HBase-1.1.5 with old ATS is working fine and with new ATS i.e yarn-5355 is
not 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
(v6.3.15#6346)

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


Mime
View raw message