[
https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720689#action_12720689
]
Hong Tang commented on HADOOP-5478:
-----------------------------------
bq. The health checking would fit in with the notion of a Ping operation, as
raised in HADOOP-5622. Every service should have a way of saying "are you up".
The failure to answer the query: trouble. If the call returns with an error:
trouble. If the call returns saying it is well, then all you know is that the
service thinks it is well, but still may not be capable of useful work.
Though, at both times, the only one who knows about the trouble is the health
checker and not the rest of the world.
> Provide a node health check script and run it periodically to check the node
> health status
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-5478
> URL: https://issues.apache.org/jira/browse/HADOOP-5478
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Aroop Maliakkal
> Assignee: Sreekanth Ramakrishnan
> Attachments: hadoop-5478-1.patch, hadoop-5478-2.patch,
> hadoop-5478-3.patch, hadoop-5478-4.patch, hadoop-5478-5.patch
>
>
> Hadoop must have some mechanism to find the health status of a node . It
> should run the health check script periodically and if there is any errors,
> it should black list the node. This will be really helpful when we run static
> mapred clusters. Else we may have to run some scripts/daemons periodically to
> find the node status and take it offline manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
