[
https://issues.apache.org/jira/browse/YARN-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728008#comment-13728008
]
Omkar Vinit Joshi commented on YARN-1008:
-----------------------------------------
[~sandyr] I am not sure if this is the case. As I am running multiple Node
managers locally and the resource scheduler (capacity one) is aware of that.
Also I don't see RM is not aware of this as NMToken too internally uses these.
I know during NMToken development I saw somewhere constructor using hostName as
parameter during NodeId creation but callers were always sending host:port..so
we were good that way.. Can you elaborate more on where in code you observed
this specifically?
> MiniYARNCluster with multiple nodemanagers, all nodes have same key for
> allocations
> -----------------------------------------------------------------------------------
>
> Key: YARN-1008
> URL: https://issues.apache.org/jira/browse/YARN-1008
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.1.0-beta
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
>
> While the NMs are keyed using the NodeId, the allocation is done based on the
> hostname.
> This makes the different nodes indistinguishable to the scheduler.
> There should be an option to enabled the host:port instead just port for
> allocations. The nodes reported to the AM should report the 'key' (host or
> host:port).
--
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
