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

Prabhu Joseph commented on YARN-6389:
-------------------------------------

[~rohithsharma] Have tested metricslimit with hbase-1.2.6 and hadoop-3.2.0 and 
it is working fine.  Can you check if there is any difference in the test.

*Rest Api Output:*
{code:java}
[hbase@yarn-ats-3 centos]$ curl -s 
"http://yarn-ats-3:8198/ws/v2/timeline/apps/application_1553684950097_0001?user.name=hbase&fields=METRICS&&metricstoretrieve=YARN_APPLICATION_MEM_PREEMPT_METRIC&metricslimit=3";
 | jq .

"metrics": [
{
"type": "TIME_SERIES",
"id": "YARN_APPLICATION_MEM_PREEMPT_METRIC",
"aggregationOp": "NOP",
"values": {
"1553684992594": 51481,
"1553684992593": 51480,
"1553684992592": 51479
}
}
]
}

Have changed YARN_APPLICATION_MEM_PREEMPT_METRIC to TIME_SERIES type for 
testing purpose.{code}
*Hbase Shell Output:*
{code:java}
hbase(main):006:0* scan 't1'
ROW COLUMN+CELL 
row column=f1:c, timestamp=1553685646951, value=value1 
1 row(s) in 0.0740 seconds


hbase(main):010:0* scan 't1', { VERSIONS => 2}
ROW COLUMN+CELL 
row column=f1:c, timestamp=1553685646951, value=value1 
row column=f1:c, timestamp=1553685642756, value=value 
1 row(s) in 0.0150 seconds{code}
 

> [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
(v7.6.3#76005)

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

Reply via email to