[
https://issues.apache.org/jira/browse/YARN-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705387#comment-13705387
]
Sandy Ryza commented on YARN-521:
---------------------------------
Thinking about this a little more, I think a specific host should be able to be
mixed with the rack it resides on. This means "I'd prefer the host, but
anything on the rack is acceptable". Here's the documentation I wrote, which
includes this:
{code}
* The way that YARN handles requesting containers in specific locations is
* somewhat subtle. Containers may be requested on specific nodes and/or on
* specific racks. By default, locations requested are only suggestions and
* the scheduler may return containers outside of them. A request may also
* be submitted with locality relaxation turned off, in which case containers
* for it will never be assigned on nodes and racks other than the ones
* explicitly specified in it. A request with locality relaxation off that
* specifies both a node and the rack it resides on means that the node is
* preferred, but another node on the rack is still acceptable.
*
* A couple restrictions apply to requests with locality relaxation turned
off.
* A request without locality relaxation may not be submitted at the same
* priority as one with locality relaxation turned on. Additionally, a
request
* without locality relaxation that explicitly includes a node, but not the
rack
* that the node resides on, may not be submitted at the same priority as a
* request without locality relaxation that explicitly asks for that rack.
{code}
> Augment AM - RM client module to be able to request containers only at
> specific locations
> -----------------------------------------------------------------------------------------
>
> Key: YARN-521
> URL: https://issues.apache.org/jira/browse/YARN-521
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api
> Affects Versions: 2.0.3-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: YARN-521-1.patch, YARN-521-2.patch, YARN-521-2.patch,
> YARN-521.patch
>
>
> When YARN-392 and YARN-398 are completed, it would be good for AMRMClient to
> offer an easy way to access their functionality
--
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
