[
https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716682#action_12716682
]
Hong Tang commented on HADOOP-5478:
-----------------------------------
- The health checking script may end up running more frequently than desired if
the thread gets interrupted.
- The health checking script may also run at a lower frequency as desired
because the code did not count the actual time spent on running the script. We
should have a variable remember the last launch time, and in the beginning of
the loop, get the current time, and either launch the script or sleep for the
difference of the check-interval and the elapsed time since the last launch
time.
- Like Owen said, we probably need to have a timeout when executing the script
(and if it indeed happens, count it as failure).
> 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 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.
