You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ramya R (JIRA)" <ji...@apache.org> on 2009/07/06 10:40:15 UTC
[jira] Created: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
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
Affects Versions: 0.20.1
Reporter: Ramya R
Priority: Minor
Fix For: 0.20.1
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.
[jira] Commented: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727493#action_12727493 ]
Hemanth Yamijala commented on MAPREDUCE-708:
--------------------------------------------
Changes look good. +1. Can you please run ant test-patch and relevant 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.
[jira] Updated: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreekanth Ramakrishnan updated MAPREDUCE-708:
---------------------------------------------
Attachment: MAPREDUCE-708-ydist.patch
Y! distribution patch.
> 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.
[jira] Commented: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728221#action_12728221 ]
Hudson commented on MAPREDUCE-708:
----------------------------------
Integrated in Hadoop-Mapreduce-trunk #15 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/15/])
. Fixes a bug to allow updating the reason for blacklisting a node on the JobTracker UI. Contributed by Sreekanth Ramakrishnan.
> 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.
[jira] Commented: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727926#action_12727926 ]
Sreekanth Ramakrishnan commented on MAPREDUCE-708:
--------------------------------------------------
All test passed locally, except the restart test cases which are being worked upon.
> 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.
[jira] Updated: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala updated MAPREDUCE-708:
---------------------------------------
Component/s: tasktracker
Affects Version/s: (was: 0.20.1)
0.21.0
Fix Version/s: (was: 0.20.1)
0.21.0
Assignee: Sreekanth Ramakrishnan
> 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
>
>
> 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.
[jira] Updated: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sreekanth Ramakrishnan updated MAPREDUCE-708:
---------------------------------------------
Attachment: MAPREDUCE-708-1.patch
Attaching patch fixing the issue pointed out by Ramya.
Patch removes the condition which checks if the TT was already blacklisted for the same reason and ignore further processing.
Added test case to verify the error messages were changed even if the reason is same.
> 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.
[jira] Resolved: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Hemanth Yamijala (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (MAPREDUCE-708) node health check script does not
refresh the "reason for blacklisting"
Posted by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org>.
[ 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.