hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jaehoon ko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
Date Tue, 13 Oct 2015 10:14:05 GMT

     [ https://issues.apache.org/jira/browse/YARN-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

jaehoon ko updated YARN-4260:
    Attachment: YARN-4260.001.patch

NodesListManager.isValidNode() now takes additional argument: int port.
This port corresponds to the port specified in yarn.nodemanager.address.
Hostname-only validity checking is still possible in case include/exclude file (specified
in yarn.resourcemanager.nodes.include-path and yarn.resourcemanager.nodes.exclude-path) does
not have port specified.

> Check NodeManager's validity based on hostname(IP) and port
> -----------------------------------------------------------
>                 Key: YARN-4260
>                 URL: https://issues.apache.org/jira/browse/YARN-4260
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: jaehoon ko
>         Attachments: YARN-4260.001.patch
> There can be situations where multiple NMs are running on the same host; emulating multi-host
YARN cluster on one host, deploying dockerized NMs that share network stack. In such cases,
RM should be able to distinguish NMs running on the same host. However, current implementation
checks validity of NM based only on hostname (NodesListManager.isValidNode()). So it is not
possible to distinguish a specific NM from other NMs on the same host.

This message was sent by Atlassian JIRA

View raw message