[
https://issues.apache.org/jira/browse/YARN-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969560#comment-14969560
]
Steve Loughran commented on YARN-4278:
--------------------------------------
One thing we do have to consider is the increased cost of this on registering
every AM. Does anyone know how expensive it is when the client asks for this?
Maybe during registration, the client should set a bool to ask for the map: if
unset, they don't . This would avoid generating and marshalling the map over
the wire for those AMs that don't want the data
> 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)
