[
https://issues.apache.org/jira/browse/YARN-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295179#comment-15295179
]
Varun Saxena commented on YARN-5105:
------------------------------------
We cannot really set the number of versions to fetch on each column qualifier /
column family. We can only set it on Scan/Get.
We do not really need to fetch anything other than latest version for each
column other than metrics.
So we can set max versions to 1 each time and set it to -1(unlimited) if we
want a time series. We can support this by indicating so in fields to retrieve.
If fields to retrieve is METRICS, it would mean single value and
METRICS_TIME_SERIES
Also, regarding query by time range, there is an issue, that we again cannot
set time range at qualifier level. It can only be set on Scan/Get which is an
issue for YARN-4455 implementation. So instead of time range we can support
limit for metric values returned in time series.
[~sjlee0], thoughts ?
> entire time series is returned for YARN container system metrics (CPU and
> memory)
> ---------------------------------------------------------------------------------
>
> Key: YARN-5105
> URL: https://issues.apache.org/jira/browse/YARN-5105
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Varun Saxena
> Labels: yarn-2928-1st-milestone
>
> I see that the entire time series of the CPU and memory metrics are returned
> for the YARN containers REST query. This has a potential of bloating the
> output big time.
> {noformat}
> "metrics": [
> {
> "type": "TIME_SERIES",
> "id": "MEMORY",
> "values":
> {
> "1463518173363": 407539712,
> "1463518170347": 407539712,
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
