[
https://issues.apache.org/jira/browse/MAPREDUCE-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-6829:
----------------------------------
Fix Version/s: (was: 2.9.0)
I reverted this from branch-2 due to the backward incompatibility that can
manifest during rolling upgrades while a job is running. See the discussion in
MAPREDUCE-6922.
> Add peak memory usage counter for each task
> -------------------------------------------
>
> Key: MAPREDUCE-6829
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6829
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2
> Reporter: Yufei Gu
> Assignee: Miklos Szegedi
> Fix For: 3.0.0-alpha4
>
> Attachments: MAPREDUCE-6829.000.patch, MAPREDUCE-6829.001.patch,
> MAPREDUCE-6829.002.patch, MAPREDUCE-6829.003.patch, MAPREDUCE-6829.004.patch,
> MAPREDUCE-6829.005.patch
>
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
