reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobin Baker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1048) Allow specifying locality constraints in YARN driver configuration
Date Tue, 23 Aug 2016 23:17:20 GMT

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

Tobin Baker commented on REEF-1048:
-----------------------------------

This YARN bug is tracked in [YARN-3928|https://issues.apache.org/jira/browse/YARN-3928], but
that has been open for over a year with no activity.

> Allow specifying locality constraints in YARN driver configuration
> ------------------------------------------------------------------
>
>                 Key: REEF-1048
>                 URL: https://issues.apache.org/jira/browse/REEF-1048
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF-Runtime-YARN
>            Reporter: Tobin Baker
>            Assignee: Tobin Baker
>            Priority: Minor
>
> In some scenarios it would be useful to specify node/rack locality for the Driver container
(YARN ApplicationMaster). One example is a cloud computing cluster where each "worker" instance
is provisioned with just enough memory to run a single Task container, but not an additional
Driver container. YARN allows you to do this with node labels (presentation: http://www.slideshare.net/Hadoop_Summit/node-labels-in-yarn-49792443),
but this isn't exposed in YARN Driver configuration. If we add node/rack parameters to {{org.apache.reef.runtime.yarn.driver.
YarnDriverConfiguration}}, we should be able to implement this functionality using node labels.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message