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

Varun Saxena commented on YARN-5105:
------------------------------------

{quote}
I think the awkwardness comes from the fact that whether metrics should be 
returned as single-value or time series is (and probably should be) somewhat 
orthogonal to whether metrics (in either form) should be included in the 
response.
Would it be feasible to indicate that the time series should be returned for 
metrics as a separate query param from the fields? I think that would result in 
a more straightforward syntax. What do you think?
{quote}
Fair enough. Lets have a boolean flag as a query param. The boolean flag will 
be ignored if metrics are not to be retrieved.

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

Reply via email to