[
https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708879#action_12708879
]
Hemanth Yamijala commented on HADOOP-5478:
------------------------------------------
bq. this fits in well with the ping/liveness stuff I've been doing
This coupled with your comment on ping() returning the latest results seems to
indicate that we have a thread that periodically executes and stores the
results. In that sense, maybe we could build this solution now, and when
HADOOP-3628 is committed to trunk, we could integrate the solution and results
to be returned as part of ping(). Does that make sense ?
bq. It may be handy to have this stuff independent of the TT itself, so you can
run a node-health checker on anything, and even if the TT refuses to play, you
could do some checking of the node.
The health check script itself is definitely external and could be anything.
All the TT would provide is the ability to run it periodically. So, I can
imagine this being run standalone, or integrated with another daemon that
provides a similar interface.
bq. Also, could it be a bit of JavaScript instead of a shell script?
Umm. Can we execute this from the TT directly ? AFAIK, this is not possible,
right ? As of now, there is no plan to support anything other than a shell
script.
bq. A scenario to worry about is what if something bad happens (e.g. a bit of
NFS goes away) that causes all health checks in a big cluster to fail
simultaneously. Would this overload the JT?
Since the plan is to send the information using the heartbeats itself, handling
the load of requests should not be a problem. I am not sure how costly
blacklist processing itself is on the JT, but hopefully not bad. We'll keep
this in mind though.
> 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
>
> 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.
