[
https://issues.apache.org/jira/browse/YARN-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949482#comment-15949482
]
Vrushali C commented on YARN-6389:
----------------------------------
As discussed in the call today:
- atsv2 now uses 1.2.4 (previously 1.1.3). We did not test with 1.1.5.
- we should ensure that the scan always fetches the latest version for metrics
unless timerange is explicitly specified. Fetching too much data will not only
affect latency but also client response set size.
> [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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
