You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Richard Theige (JIRA)" <ji...@apache.org> on 2009/03/14 16:33:50 UTC

[jira] Commented: (HADOOP-5478) Provide a node health check script and run it periodically to check the node health status

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

Richard Theige commented on HADOOP-5478:
----------------------------------------

 For consideration:

   * check_network_speed
    * check_filesystems
          o check for read-only filesystems 
    * check_ylock
          o required, if not installed some jobs which are using ycore libs will fail 
    * check_symlinks
          o checks for hadoop versions 
    * check_diskspace
          o checks if there is sufficient mapred tmp space
          o TT should handle this 


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