[
https://issues.apache.org/jira/browse/MAPREDUCE-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258368#comment-13258368
]
Robert Joseph Evans commented on MAPREDUCE-4026:
------------------------------------------------
I like the patch, I don't really have much of an opinion of the changing of the
default values. I only have one NIT and that is with preexisting code. I
would like to have MINIMUM_MEMORY and MAXIMUM_MEMORY in both the fifo and the
capacity scheduler renamed to DEFAULT_MINIMUM_ALLOCATION and
DEFAULT_MAXIMUM_ALLOCATION respectively. This is just so it is less confusing
what these values are, especially now that they are exposed to the tests.
> Lower minimum-allocation-mb to sensible defaults
> ------------------------------------------------
>
> Key: MAPREDUCE-4026
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4026
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, scheduler
> Affects Versions: 2.0.0
> Reporter: Harsh J
> Assignee: Harsh J
> Attachments: MAPREDUCE-4026.patch, MAPREDUCE-4026.patch,
> MAPREDUCE-4026.patch, MAPREDUCE-4026.patch
>
>
> The CapacityScheduler's minimum-allocation-mb is set to 1024.
> The FIFO's minimum-allocation-mb meanwhile, is 128.
> I propose changing the formers' minimum to that amount as well. 1024 is way
> too much as a default, wastes "slots" on NMs - and I also do not see why CS
> has to deviate that settings from the FIFO default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
