You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2015/04/30 03:24:06 UTC
[jira] [Commented] (YARN-3565)
NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object
instead of String
[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520672#comment-14520672 ]
Naganarasimha G R commented on YARN-3565:
-----------------------------------------
Hi [~wangda], I would like to work on this jira and i was also similarly thinking in distributed case how to support exclusivity/constraints !
> NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-3565
> URL: https://issues.apache.org/jira/browse/YARN-3565
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, client, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
>
> Now NM HB/Register uses Set<String>, it will be hard to add new fields if we want to support specifying NodeLabel type such as exclusivity/constraints, etc. We need to make sure rolling upgrade works.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)