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

Varun Saxena commented on YARN-6435:
------------------------------------

bq. sorry did not get this. 
I meant with current value of 1000 we would be able to print time series for 
only 3 hours approx which is too less.
So I agree that it should be increased.

Yes HBase will be able to handle max versions equal to int max as well. What I 
meant is that this will increase the amount of storage required. The reason max 
versions were kept at only 1000 I think was due to the concern that a large 
value would increase the storage space required. Which would be fine in some 
clusters, may not be so in some others.
That is why put forth a suggestion that maybe we can make this configurable so 
that it can be set as per cluster capacity.

I wasn't really involved in deciding default value of 1000 hence not a 100% 
sure behind the intention so let us get opinion from [~vrushalic] who may have 
been involved with this.

> [ATSv2] Can't retrieve more than 1000 versions of metrics in time series
> ------------------------------------------------------------------------
>
>                 Key: YARN-6435
>                 URL: https://issues.apache.org/jira/browse/YARN-6435
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>            Priority: Critical
>         Attachments: YARN-6435.0001.patch
>
>
> It is observed that, even though *metricslimit* is set to 1500, maximum 
> number of metrics values retrieved is 1000. 
> This is due to, while creating EntityTable, metrics column family max version 
> is specified as 1000 which is hardcoded in 
> {{EntityTable#DEFAULT_METRICS_MAX_VERSIONS}}. So, HBase will return max 
> version with following {{MIN(cf max version , user provided max version)}}. 
> This behavior is contradicting the documentation which claims that 
> {code}
> metricslimit - If specified, defines the number of metrics to return. 
> Considered only if fields contains METRICS/ALL or metricstoretrieve is 
> specified. Ignored otherwise. The maximum possible value for metricslimit can 
> be maximum value of Integer. If it is not specified or has a value less than 
> 1, and metrics have to be retrieved, then metricslimit will be considered as 
> 1 i.e. latest single value of metric(s) will be returned.
> {code} 



--
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

Reply via email to