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:08:59 UTC
[jira] [Created] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and
getUsedMemory() exist in MR1 but not MR2
Sandy Ryza created MAPREDUCE-4845:
-------------------------------------
Summary: 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
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
[jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and
getUsedMemory() exist in MR1 but not MR2
Posted by "Sandy Ryza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandy Ryza updated MAPREDUCE-4845:
----------------------------------
Status: Patch Available (was: Open)
> 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: 2.0.2-alpha, 1.1.1
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: MAPREDUCE-4845-branch-1.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
[jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and
getUsedMemory() exist in MR1 but not MR2
Posted by "Sandy Ryza (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (MAPREDUCE-4845) ClusterStatus.getMaxMemory()
and getUsedMemory() exist in MR1 but not MR2
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510896#comment-13510896 ]
Hadoop QA commented on MAPREDUCE-4845:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12556024/MAPREDUCE-4845-branch-1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3094//console
This message is automatically generated.
> 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
>
>
> 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
[jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and
getUsedMemory() exist in MR1 but not MR2
Posted by "Sandy Ryza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandy Ryza updated MAPREDUCE-4845:
----------------------------------
Affects Version/s: 1.1.1
2.0.2-alpha
> 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
>
>
> 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
[jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and
getUsedMemory() exist in MR1 but not MR2
Posted by "Sandy Ryza (JIRA)" <ji...@apache.org>.
[ 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-branch-1.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
> 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
>
>
> 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
[jira] [Updated] (MAPREDUCE-4845) ClusterStatus.getMaxMemory() and
getUsedMemory() exist in MR1 but not MR2
Posted by "Sandy Ryza (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sandy Ryza updated MAPREDUCE-4845:
----------------------------------
Component/s: client
> 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
>
>
> 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