[jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
[ https://issues.apache.org/jira/browse/YARN-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4260: Labels: oct-16-easy oct16-easy (was: oct16-easy) > 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 > Labels: oct16-easy > Attachments: YARN-4260.001.patch, YARN-4260.002.patch, > YARN-4260.003.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) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
[ https://issues.apache.org/jira/browse/YARN-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4260: Labels: oct16-easy (was: oct-16-easy oct16-easy) > 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 > Labels: oct16-easy > Attachments: YARN-4260.001.patch, YARN-4260.002.patch, > YARN-4260.003.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) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
[ https://issues.apache.org/jira/browse/YARN-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4260: Labels: oct16-easy (was: ) > 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 > Labels: oct16-easy > Attachments: YARN-4260.001.patch, YARN-4260.002.patch, > YARN-4260.003.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) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
[ 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.003.patch patch against 40cac59248f17c59fc819f4145cdeac9db309626 (current trunk) > 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, > YARN-4260.003.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)
[jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
[ 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.002.patch Updated patch against commit 40cac59248f17c59fc819f4145cdeac9db309626 > 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)
[jira] [Updated] (YARN-4260) Check NodeManager's validity based on hostname(IP) and port
[ 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 (v6.3.4#6332)
