[
https://issues.apache.org/jira/browse/HADOOP-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640560#action_12640560
]
Hemanth Yamijala commented on HADOOP-4439:
------------------------------------------
One other proposal was to change the max memory specification to be a
percentage of the physical RAM rather than an absolute value. In interest of
time (as this is a blocker for 0.19), I decided to leave this suggestion out.
As the configuration is not exposed until HADOOP-4035, we can change it as part
of that patch. In fact, the current configuration can be supported in a
backwards compatible model as well, if we want.
> Cleanup memory related resource management
> ------------------------------------------
>
> Key: HADOOP-4439
> URL: https://issues.apache.org/jira/browse/HADOOP-4439
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4439.patch
>
>
> HADOOP-3759 and HADOOP-3581 introduced memory based resource management. This
> JIRA is to cleanup certain aspects of the two issues that came up while doing
> HADOOP-4035, which is filed to support memory based scheduling
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
