Weiwei Yang commented on YARN-1042:

Hi Steve

Thanks for the comments. I correct the words. And regarding to 
That way the AM can choose to wait 1 minute or more for an anti-affine 
placement before giving up and accepting a node already in use.
this is exactly the reason I proposed the PREFERRED rules,  you can set a max 
time await before compromising the rule. For example, you use ANTI_AFFINITY 
rule and set 1 minute to the max wait time, then RM will wait for at least 1 
minute before assigning a container to a node which already has a container 
running on it. Or ... forget about REQUIRED or PREFERRED, we can directly 
define these preference in ContainerAllocateRule class, with an attribute like 
*maxTimeAwaitBeforeCompromise*, default it is 0, which means never compromise 
the rule (REQUIRED). 

> 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
>            Reporter: Steve Loughran
>            Assignee: Arun C Murthy
>         Attachments: YARN-1042-demo.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

Reply via email to