You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2012/12/05 01:22:59 UTC

[jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and getUsedMemory() exist in MR1 but not MR2

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

Sandy Ryza updated MAPREDUCE-4845:
----------------------------------

    Attachment: MAPREDUCE-4845.patch
    
> 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
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>         Attachments: 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