[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-4271: - Issue Type: Sub-task (was: Improvement) Parent: YARN-5078 > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Subru Krishnan >Assignee: Raghav Mohan >Priority: Minor > > This JIRA proposes making the NodeHealthCheckerService in the NM pluggable as > in cloud environments like Azure we want to tap into the provided health > checkers for disk and other service signal statuses. The idea is to extend > the existing NodeHealthCheckerService and hook in custom implementation to > evaluate if the node is healthy or not. -- 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-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Assignee: Raghav Mohan > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Assignee: Raghav Mohan >Priority: Minor > > This JIRA proposes making the NodeHealthCheckerService in the NM pluggable as > in cloud environments like Azure we want to tap into the provided health > checkers for disk and other service signal statuses. The idea is to extend > the existing NodeHealthCheckerService and hook in custom implementation to > evaluate if the node is healthy or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Description: This JIRA proposes making the (was: We introduce the notion of an RMProxy, running on each node (or once per rack). Upon start the AM is forced (via tokens and configuration) to direct all its requests to a new services running on the NM that provide a proxy to the central RM. This give us a place to: 1) perform distributed scheduling decisions 2) throttling mis-behaving AMs 3) mask the access to a federation of RMs) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Priority: Minor > > This JIRA proposes making the -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Description: This JIRA proposes making the NodeHealthCheckerService in the NM pluggable as in cloud environments like Azure we want to tap into the provided health checkers for disk and other service signal statuses. The idea is to extend the existing NodeHealthCheckerService and hook in custom implementation to evaluate if the node is healthy or not. (was: This JIRA proposes making the ) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Priority: Minor > > This JIRA proposes making the NodeHealthCheckerService in the NM pluggable as > in cloud environments like Azure we want to tap into the provided health > checkers for disk and other service signal statuses. The idea is to extend > the existing NodeHealthCheckerService and hook in custom implementation to > evaluate if the node is healthy or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Priority: Minor (was: Major) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager >Reporter: Subru Krishnan >Assignee: Kishore Chaliparambil >Priority: Minor > Fix For: 2.8.0 > > > We introduce the notion of an RMProxy, running on each node (or once per > rack). Upon start the AM is forced (via tokens and configuration) to direct > all its requests to a new services running on the NM that provide a proxy to > the central RM. > This give us a place to: > 1) perform distributed scheduling decisions > 2) throttling mis-behaving AMs > 3) mask the access to a federation of RMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-2877) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Assignee: Kishore Chaliparambil >Priority: Minor > Fix For: 2.8.0 > > > We introduce the notion of an RMProxy, running on each node (or once per > rack). Upon start the AM is forced (via tokens and configuration) to direct > all its requests to a new services running on the NM that provide a proxy to > the central RM. > This give us a place to: > 1) perform distributed scheduling decisions > 2) throttling mis-behaving AMs > 3) mask the access to a federation of RMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Assignee: (was: Subru Krishnan) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Priority: Minor > Fix For: 2.8.0 > > > We introduce the notion of an RMProxy, running on each node (or once per > rack). Upon start the AM is forced (via tokens and configuration) to direct > all its requests to a new services running on the NM that provide a proxy to > the central RM. > This give us a place to: > 1) perform distributed scheduling decisions > 2) throttling mis-behaving AMs > 3) mask the access to a federation of RMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Fix Version/s: (was: 2.8.0) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Priority: Minor > > We introduce the notion of an RMProxy, running on each node (or once per > rack). Upon start the AM is forced (via tokens and configuration) to direct > all its requests to a new services running on the NM that provide a proxy to > the central RM. > This give us a place to: > 1) perform distributed scheduling decisions > 2) throttling mis-behaving AMs > 3) mask the access to a federation of RMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Target Version/s: (was: 2.8.0) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Assignee: Kishore Chaliparambil >Priority: Minor > Fix For: 2.8.0 > > > We introduce the notion of an RMProxy, running on each node (or once per > rack). Upon start the AM is forced (via tokens and configuration) to direct > all its requests to a new services running on the NM that provide a proxy to > the central RM. > This give us a place to: > 1) perform distributed scheduling decisions > 2) throttling mis-behaving AMs > 3) mask the access to a federation of RMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (YARN-4271) Make the NodeManager's health checker service pluggable
[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4271: - Component/s: (was: resourcemanager) > Make the NodeManager's health checker service pluggable > --- > > Key: YARN-4271 > URL: https://issues.apache.org/jira/browse/YARN-4271 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager >Reporter: Subru Krishnan >Assignee: Kishore Chaliparambil >Priority: Minor > Fix For: 2.8.0 > > > We introduce the notion of an RMProxy, running on each node (or once per > rack). Upon start the AM is forced (via tokens and configuration) to direct > all its requests to a new services running on the NM that provide a proxy to > the central RM. > This give us a place to: > 1) perform distributed scheduling decisions > 2) throttling mis-behaving AMs > 3) mask the access to a federation of RMs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
