[
https://issues.apache.org/jira/browse/MAPREDUCE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725736#action_12725736
]
Allen Wittenauer commented on MAPREDUCE-211:
--------------------------------------------
> Internal Yahoo! patch for the issue.
Posting to the Internet sort of makes it not internal anymore. :(
> Provide a node health check script and run it periodically to check the node
> health status
> ------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-211
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-211
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Aroop Maliakkal
> Assignee: Sreekanth Ramakrishnan
> Fix For: 0.21.0
>
> Attachments: active.png, blacklist1.png, blacklist2.png,
> cluster_setup.pdf, hadoop-5478-1.patch, hadoop-5478-2.patch,
> hadoop-5478-3.patch, hadoop-5478-4.patch, hadoop-5478-5.patch,
> hadoop-5478-6.patch, mapred-211-common-3.patch, mapred-211-core-1.patch,
> mapred-211-internal.patch, mapred-211-mapred-1.patch,
> mapred-211-mapred-2.patch, mapred-211-mapred-3.patch,
> mapred-211-mapred-4.patch, mapred-211-mapred-5.patch,
> mapred-211-mapred-7.patch, mapred-211-mapred-8.patch,
> mapred-211-mapred-9.patch, MAPREDUCE-211-forrest.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.
