hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-689) Add multiplier unit to resourcecapabilities
Date Mon, 20 May 2013 20:15:18 GMT

    [ https://issues.apache.org/jira/browse/YARN-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662322#comment-13662322
] 

Arun C Murthy commented on YARN-689:
------------------------------------

bq. All the nodes in a cluster have 3 GB. Because YARN does not yet allow us to set limits
on disk IO, we don't want more than 3 containers on each node.

I'm sorry, this isn't making sense to me.

The reason we do multi-resource scheduling is to *stop* trying to come up with proxies. Why
aren't we doing DRF? I'm not comfortable with this change.
                
> Add multiplier unit to resourcecapabilities
> -------------------------------------------
>
>                 Key: YARN-689
>                 URL: https://issues.apache.org/jira/browse/YARN-689
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: api, scheduler
>    Affects Versions: 2.0.4-alpha
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>         Attachments: YARN-689.patch, YARN-689.patch, YARN-689.patch
>
>
> Currently we overloading the minimum resource value as the actual multiplier used by
the scheduler.
> Today with a minimum memory set to 1GB, requests for 1.5GB are always translated to allocation
of 2GB.
> We should decouple the minimum allocation from the multiplier.
> The multiplier should also be exposed to the client via the RegisterApplicationMasterResponse

--
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

Mime
View raw message