[
https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718752#action_12718752
]
Hong Tang edited comment on HADOOP-5478 at 6/12/09 12:49 AM:
-------------------------------------------------------------
@owen: Steve's comments seem to imply that we need the capability of launch the
health checking script in response to external commands.
@Sreekanth: If I understand correctly, the new patch introduces another thread
to check for command execution timeout. Is there a way to eliminate it
(possibly by modifying shell execution API to accept timeouts)?
was (Author: hong.tang):
@owen: Steve's comments seem to imply that we need the capability of launch
the health checking script in response to external commands.
@Streekanth: If I understand correctly, the new patch introduces another thread
to check for command execution timeout. Is there a way to eliminate it
(possibly by modifying shell execution API to accept timeouts)?
> 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: Vinod K V
> Attachments: hadoop-5478-1.patch, hadoop-5478-2.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.
