[
https://issues.apache.org/jira/browse/YARN-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15736672#comment-15736672
]
Konstantinos Karanasos commented on YARN-1042:
----------------------------------------------
[~leftnoteasy], I think you are right that exposing min/max cardinality might
be complicated for the user...
So, you are suggesting to expose expose to the user explicit affinity and
anti-affinity constraints, but interpret them under the hood as more complex
unified constraints?
I think it is a good approach. This way we keep it simple for the end user, and
we create the hooks for more complicated cardinality and tag constraints as
future work.
> add ability to specify affinity/anti-affinity in container requests
> -------------------------------------------------------------------
>
> Key: YARN-1042
> URL: https://issues.apache.org/jira/browse/YARN-1042
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 3.0.0-alpha1
> Reporter: Steve Loughran
> Assignee: Wangda Tan
> Attachments: YARN-1042-demo.patch, YARN-1042-design-doc.pdf,
> YARN-1042-global-scheduling.poc.1.patch, YARN-1042.001.patch,
> YARN-1042.002.patch
>
>
> container requests to the AM should be able to request anti-affinity to
> ensure that things like Region Servers don't come up on the same failure
> zones.
> Similarly, you may be able to want to specify affinity to same host or rack
> without specifying which specific host/rack. Example: bringing up a small
> giraph cluster in a large YARN cluster would benefit from having the
> processes in the same rack purely for bandwidth reasons.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
