hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Vasudev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5044) Add peak memory usage counter for each task
Date Thu, 05 May 2016 17:16:12 GMT

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

Varun Vasudev commented on YARN-5044:
-------------------------------------

[~yufeigu] - is this work for every container? Have you looked at the ContainerMetrics class
- it should have this information for physical memory at least.

> Add peak memory usage counter for each task
> -------------------------------------------
>
>                 Key: YARN-5044
>                 URL: https://issues.apache.org/jira/browse/YARN-5044
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: yarn
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>
> Each task has counters PHYSICAL_MEMORY_BYTES and VIRTUAL_MEMORY_BYTES, which are snapshots
of memory usage of that task. They are not sufficient for users to understand peak memory
usage by that task, e.g. in order to diagnose task failures, tune job parameters or change
application design. This new feature will add two more counters for each task: PHYSICAL_MEMORY_BYTES_MAX
and VIRTUAL_MEMORY_BYTES_MAX.
> This JIRA has the same feature from MAPREDUCE-4710.  I file this new YARN JIRA since
MAPREDUCE-4710 is pretty old one from MR 1.x era, it more or less assumes a branch-1 architecture,
should be close at this point.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message