hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-689) Add multiplier unit to resourcecapabilities
Date Thu, 06 Jun 2013 08:42:22 GMT

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

Tom White commented on YARN-689:
--------------------------------

> The multiplier seems to be one approach to do this, though as Arun says it might make
the code in the scheduler complicated to get right.

The change doesn't make the code more complicated. Instead of the range of allowable requests
being [1, n] (normalized by the minimum), it becomes [m, n], for configurable m and n, with
m = 1 as the default.
                
> Add multiplier unit to resourcecapabilities
> -------------------------------------------
>
>                 Key: YARN-689
>                 URL: https://issues.apache.org/jira/browse/YARN-689
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          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, 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