[
https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464936#comment-13464936
]
Nathan Roberts commented on YARN-2:
-----------------------------------
bq. Num cores to be a float to allow a bit of over-subscription like it is
possible today without any concept of cores. Granted this can be simulated by
artificially increasing the number of cores in configuration, but we should
think of a more appropriate way.
I'd vote for doing this sooner rather than later. Simulation doesn't seem very
clean because it would force us to expose the lie to the applications
requesting resources (right?). Even if we keep it as an int and express it in
tenths, I think that would be quite sufficient. Also, it's not entirely about
over-subscription, small tasks which do a lot of sitting around waiting for
things to happen, can't accurately reflect that.
> Enhance CS to schedule accounting for both memory and cpu cores
> ---------------------------------------------------------------
>
> Key: YARN-2
> URL: https://issues.apache.org/jira/browse/YARN-2
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: capacityscheduler, scheduler
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 2.0.2-alpha
>
> Attachments: MAPREDUCE-4327.patch, MAPREDUCE-4327.patch,
> MAPREDUCE-4327.patch, MAPREDUCE-4327-v2.patch, MAPREDUCE-4327-v3.patch,
> MAPREDUCE-4327-v4.patch, MAPREDUCE-4327-v5.patch, YARN-2-help.patch,
> YARN-2.patch, YARN-2.patch
>
>
> With YARN being a general purpose system, it would be useful for several
> applications (MPI et al) to specify not just memory but also CPU (cores) for
> their resource requirements. Thus, it would be useful to the
> CapacityScheduler to account for both.
--
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
