hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String
Date Thu, 30 Apr 2015 01:24:06 GMT

    [ 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)

Mime
View raw message