[
https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727884#action_12727884
]
Sreekanth Ramakrishnan commented on MAPREDUCE-708:
--------------------------------------------------
output from ant test-patch:
{noformat}
[exec]
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
[exec]
[exec]
[exec]
{noformat}
Running tests.
> 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
>
>
> 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.
