[
https://issues.apache.org/jira/browse/HADOOP-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708883#action_12708883
]
Hemanth Yamijala commented on HADOOP-5478:
------------------------------------------
bq. We really need the equivalent of dfsadmin -report for the JobTracker to
provide this same level of output.
Allen, I had command line reporting in mind when writing the specs. Worst case,
if the effort seems large to cover we will do this as a follow-up JIRA,
restricting the information to the web UI for now.
bq. Additionally, torque ignores the exit status
If this is acceptable to all, we can do the same as well.
> 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.
