hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1391) Lost node list should be identify by NodeId
Date Fri, 13 Dec 2013 00:32:07 GMT

    [ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846969#comment-13846969
] 

Gera Shegalov commented on YARN-1391:
-------------------------------------

Siqi asked me to chime in. 
An example of a real yet untypical scenario I am aware of is an HPC scale up machine. A single
node manager does not scale to manage all containers that can run concurrently there. So you
have a choice of either unnecessarily fragmenting this machine into a bunch of smaller VM/OS's
or run a bunch of NM's without any overhead of virtualization.

It's always been possible to run multiple TT's in MRv1 as well.

> Lost node list should be identify by NodeId
> -------------------------------------------
>
>                 Key: YARN-1391
>                 URL: https://issues.apache.org/jira/browse/YARN-1391
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.5-alpha
>            Reporter: Siqi Li
>            Assignee: Siqi Li
>         Attachments: YARN-1391.v1.patch
>
>
> in case of multiple node managers on a single machine. each of them should be identified
by NodeId, which is more unique than just host name



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message