Steve Loughran commented on YARN-4278:

Bikas, SLIDER-947 suggests exactly that as a workaround; my concerns there 
relate to token expiry and the like...we'll be using a delegation token unless 
we have a keytab. FWIW I'm using a yarn client in SPARK-1537 without problems 
so far

regarding network load, that's why I've suggested it should be an option on 
register/resync. Given that clients can ask for it, and AM registration is, 
excluding failures, the same as the #of client launches, I doubt it'd be that 
more expensive. Except: what would happen on any failover?

> 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

Reply via email to