[ https://issues.apache.org/jira/browse/YARN-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301491#comment-15301491 ]
Varun Saxena commented on YARN-5105: ------------------------------------ bq. Given that we already have the concept of limit to limit the # entities we return, why don't change the timeseries argument from boolean to a timeserieslimit. I was infact talking about a limit in my very first comment. I am ok with implementing a limit as well for metrics. bq. Furthermore we can specify for now that the only two values allowed are -1 and 1. Why restrict to only 2 values then ? We can set the max versions accordingly. If we have to support only 2 values, wouldn't boolean flag be better ? > 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 > Attachments: YARN-5105-YARN-2928.01.patch, > YARN-5105-YARN-2928.02.patch, YARN-5105-YARN-2928.03.patch > > > 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