[ 
https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708402#action_12708402
 ] 

Steve Loughran commented on HADOOP-5478:
----------------------------------------

-this fits in well with the ping/liveness stuff I've been doing. I already do 
this with things that GET the various JSP pages of a node, checking the health 
of the jetty endpoints. when those pages return a non-200 code, I return an 
error that includes the entire HTTP page sent back, as that is often useful. 

# 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.
# Also, could it be a bit of JavaScript instead of a shell script?
# 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?
# Incidentally, I could imagine some scripts being slow, so I wouldnt have my 
ping code run the .sh every call, but instead run it on a regular frequency; a 
ping() would return the latest results. 


> 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.

Reply via email to