[
https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540553#comment-13540553
]
Karthik Kambatla commented on YARN-2:
-------------------------------------
{quote}
for consistency, we would also need to report this measure wherever resource
requests and consumption are reported (web UI, metrics, command line). Once we
expect the user to think about it in a certain way, is there a strong reason
for having a different model internally?
{quote}
Very valid points, Sandy. I agree we should have a strong motivation to support
a model with particular usecases and advantages. Let me think more about this.
I like Bikas' idea of supporting a baseline virtual core (1 GHz core) - that
doesn't need us to maintain two different versions (one for the user, and one
internally), and it also brings standardization to otherwise heterogeneous
clusters.
Let us think more about this and start a new JIRA with a relatively more
concrete proposal. We have already hijacked this JIRA ;)
> 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, 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
