You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2015/10/20 08:39:27 UTC
[jira] [Created] (YARN-4278) On AM registration, response should
include cluster Nodes report on demanded by registration request.
Rohith Sharma K S created YARN-4278:
---------------------------------------
Summary: 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/%3C0EE80F6F7A98A64EBD18F2BE839C91156798AFB3@szxeml512-mbs.china.huawei.com%3E] [Thread-2|http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201510.mbox/%3C4F7812FC-AB5D-465D-AC89-82473569817E@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 [~stevel@apache.org] is while AM registration let response hold the cluster nodes report
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)