hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreekanth Ramakrishnan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-709) node health check script does not display the correct message on timeout
Date Tue, 07 Jul 2009 03:00:14 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727889#action_12727889

Sreekanth Ramakrishnan commented on MAPREDUCE-709:

output from ant test-patch

     [exec] +1 overall.
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 3 new or modified tests.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.

> node health check script does not display the correct message on timeout
> ------------------------------------------------------------------------
>                 Key: MAPREDUCE-709
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-709
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Ramya R
>            Assignee: Sreekanth Ramakrishnan
>            Priority: Minor
>             Fix For: 0.21.0
>         Attachments: mapred-709-1.patch
> When the node health check script takes more than "mapred.healthChecker.script.timeout"
to return, it should display a timeout message. Instead it displays the full stacktrace as
> {noformat}
> java.io.IOException: Stream closed at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)

> at java.io.BufferedInputStream.read(BufferedInputStream.java:308) 
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264) 
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306) 
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158) 
> at java.io.InputStreamReader.read(InputStreamReader.java:167) 
> at java.io.BufferedReader.fill(BufferedReader.java:136) 
> at java.io.BufferedReader.readLine(BufferedReader.java:299) 
> at java.io.BufferedReader.readLine(BufferedReader.java:362) 
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:202) 
> at org.apache.hadoop.util.Shell.run(Shell.java:145) 
> at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:338) 
> at org.apache.hadoop.mapred.NodeHealthCheckerService$NodeHealthMonitorExecutor.run(NodeHealthCheckerService.java:119)

> at java.util.TimerThread.mainLoop(Timer.java:512) 
> at java.util.TimerThread.run(Timer.java:462) 
> {noformat}
> Also the "mapred.healthChecker.script.timeout" is not being reflected in the job.xml.
It always picks up the default value. It is just an UI issue.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message