[
https://issues.apache.org/jira/browse/YARN-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753048#comment-13753048
]
Hitesh Shah commented on YARN-1057:
-----------------------------------
[~yeshavora] Could you give more details on the use-case you are trying to
address? I am inclined to mark this as an invalid/wontfix jira as there is no
clear objective on how the RM should handle an invalid entry in the
include/exclude files? Is the expectation that the RM shutdown when an invalid
entry is added to the file and the refresh command invoked? The use-case that
may make more sense is that a connection from a nodemanager, whose reverse dns
lookup fails, should be rejected.
[~xgong] Regarding the patch, what is the objective of filtering the in-memory
list of included/excluded nodes? If there is a transient dns issue, would this
mean that the NM will never be allowed to register with the RM?
> Add mechanism to check validity of a Node to be Added/Excluded
> --------------------------------------------------------------
>
> Key: YARN-1057
> URL: https://issues.apache.org/jira/browse/YARN-1057
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.1.0-beta
> Reporter: yeshavora
> Assignee: Xuan Gong
> Attachments: YARN-1057.1.patch
>
>
> Yarn does not complain while passing an invalid hostname like
> 'invalidhost.com' inside include/exclude node file. (specified by
> 'yarn.resourcemanager.nodes.include-path' or
> 'yarn.resourcemanager.nodes.exclude-path').
> Need to add a mechanism to check the validity of the hostname before
> including or excluding from cluster. It should throw an error / exception
> while adding/removing an invalid node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
