hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and getUsedMemory() exist in MR1 but not MR2
Date Wed, 12 Dec 2012 12:19:21 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom White updated MAPREDUCE-4845:
---------------------------------

    Attachment: MAPREDUCE-4845.patch

+1 this is a reasonable approach. I'm re-attaching the trunk patch so Jenkins can check it.
                
> ClusterStatus.getMaxMemory() and getUsedMemory() exist in MR1 but not MR2 
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4845
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4845
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.1.1, 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: MAPREDUCE-4845-branch-1.patch, MAPREDUCE-4845.patch, MAPREDUCE-4845.patch
>
>
> For backwards compatibility, these methods should exist in both MR1 and MR2.
> Confusingly, these methods return the max memory and used memory of the jobtracker, not
the entire cluster.
> I'd propose to add them to MR2 and return -1, and deprecate them in both MR1 and MR2.
 Alternatively, I could add plumbing to get the resource manager memory stats.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message