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

Hadoop QA commented on YARN-4260:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  3s | The patch command could not apply 
the patch. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12766474/YARN-4260.002.patch |
| Optional Tests | shellcheck javadoc javac unit findbugs checkstyle site |
| git revision | trunk / 2a98724 |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/9436/console |


This message was automatically generated.

> 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, YARN-4260.002.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
(v6.3.4#6332)

Reply via email to