[
https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540107#comment-13540107
]
Bikas Saha commented on YARN-2:
-------------------------------
I am not against shares if there are technical reasons going for it. However,
"same terminology as cgroups" makes me wary of introducing more Linux concepts
into Hadoop code.
Arun, do we have a baseline value for what a virtual core is (eg 1Ghz Intel
Xeon 2010 core)? Like Amazon's classification of CPU for their VM's. Is it
published in the docs or somewhere in the code? Are are we planning to make it
configurable and so 1 virtual core on cluster A is not comparable to 1 virtual
core on cluster B? I am trying to understand if virtual cores is a
standardization or merely a multiplicative artifact that gives us finer
granularity.
> 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.3-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, YARN-2.patch, YARN-2.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
