You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Varun Saxena (JIRA)" <ji...@apache.org> on 2017/03/24 18:27:41 UTC
[jira] [Commented] (YARN-6389) [ATSv2] metricslimit query parameter
do not work
[ https://issues.apache.org/jira/browse/YARN-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940870#comment-15940870 ]
Varun Saxena commented on YARN-6389:
------------------------------------
Probably something has broken either due to change in HBase version or some other change on the reader side itself.
Let me check
> [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