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

Bikas Saha commented on YARN-4278:
----------------------------------

Client can ask for it but IMO, no clients actually do. Hence we probably don't 
have enough evidence to suggest that it might work in practice, specially at 
large deployments like Yahoo.

> On AM registration, response should  include cluster Nodes report on demanded 
> by registration request.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4278
>                 URL: https://issues.apache.org/jira/browse/YARN-4278
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: api
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>
> From the yarn-dev mailing list discussion thread 
> [Thread-1|http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201510.mbox/%3c0ee80f6f7a98a64ebd18f2be839c91156798a...@szxeml512-mbs.china.huawei.com%3E]
>  
> [Thread-2|http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201510.mbox/%3c4f7812fc-ab5d-465d-ac89-824735698...@hortonworks.com%3E]
>  
> Slider required to know about cluster nodes details for providing support for 
> affinity/anti-affinity on containers.
> Current behavior : During life span of application , updatedNodes are sent in 
> allocate request only if there are any change like added/removed/'state 
> change' in the nodes. Otherwise cluster nodes not updated to AM.
> One of the approach thought by [~ste...@apache.org] is while AM registration 
> let response hold the cluster nodes report



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

Reply via email to