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 "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2013/06/08 00:54:21 UTC
[jira] [Comment Edited] (MAPREDUCE-5310) MRAM should not normalize
allocation request capabilities
[ https://issues.apache.org/jira/browse/MAPREDUCE-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678540#comment-13678540 ]
Alejandro Abdelnur edited comment on MAPREDUCE-5310 at 6/7/13 10:53 PM:
------------------------------------------------------------------------
On slot millis, then we should remove all the related logic and just leave the counter constant for backwards compatibility and deprecating the constant. Better return zero than some gibberish, I'll open a JIRA and post patch for it.
was (Author: tucu00):
On slot minis, then we should remove all the related logic and just leave the counter constant for backwards compatibility and deprecating the constant. Better return zero than some gibberish, I'll open a JIRA and post patch for it.
> MRAM should not normalize allocation request capabilities
> ---------------------------------------------------------
>
> Key: MAPREDUCE-5310
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5310
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: applicationmaster
> Affects Versions: 2.0.4-alpha
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Attachments: MAPREDUCE-5310.patch
>
>
> The MRAM is assuming knowledge of the scheduler internals to normalize allocation request capabilities.
> Per discussions in YARN-689 and YARN-769 it should not do that.
--
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