You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/07/07 09:30:15 UTC
[jira] Resolved: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala resolved MAPREDUCE-708.
----------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
I just committed this. Thanks, Sreekanth !
> node health check script does not refresh the "reason for blacklisting"
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-708
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-708
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.21.0
> Reporter: Ramya R
> Assignee: Sreekanth Ramakrishnan
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-708-1.patch, MAPREDUCE-708-ydist.patch
>
>
> After MAPREDUCE-211, the node health check script does not refresh the "reason for blacklisting".
> The steps to reproduce the issue are:
> * Blacklist a TT with an error message 'x'
> * Change the health check script to return an error message 'y'
> * The "reason for blacklisting" still shows 'x'
>
> The impact of this issue is that the feature fails to trap transient errors.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.