[
https://issues.apache.org/jira/browse/MAPREDUCE-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231832#comment-13231832
]
Harsh J commented on MAPREDUCE-4026:
------------------------------------
Arun,
It is only the min-alloc am changing, not the job defaults
(mapreduce.map.memory.mb and such) which are presently 1024 or higher, and will
need a new JIRA if to be lowered as a default (agree that 128 is too low -
either 200 or 512 should be it for those).
I don't think lowering min alloc default would change default job requirements,
but will at least allow folks to pass -D options for memory needs that are
lower than 1024 - for more tasks in parallel.
Or am I missing something?
> 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: 0.23.3
> Reporter: Harsh J
> Assignee: Harsh J
>
> 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
