[
https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350226#comment-15350226
]
Vinod Kumar Vavilapalli commented on YARN-4271:
-----------------------------------------------
Just caught up with this.
I am not sure if we even now understand the original need / use-case.
bq. make the NodeHealthCheckerService more smarter instead of a boolean
healthy/unhealthy state.
bq. We were just looking into YARN-3503 and looks that will suffice for (2)
presently.
Can you describe what was the original need for 'smarter' service, what it
means and how it is satisfied with YARN-3503? Trying to understand what is
better built into the platform and what is better left up to the higher layers
by using things like JMX.
> 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: [email protected]
For additional commands, e-mail: [email protected]
