Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 19 Nov 2011 20:00:52 +0000 (UTC)
From: "Harsh J (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1353938283.47674.1321732853101.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-79) Uncaught Exception in DataTransfer.run
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153570#comment-13153570 ] 

Harsh J commented on HDFS-79:
-----------------------------

This would be a RuntimeException -> IllegalStateException derivative. The docs say that this exception is unchecked.

I wonder if we see it anymore though?

We could intercept it, but not sure if the behavior is alright this way already.
                
> Uncaught Exception in DataTransfer.run
> --------------------------------------
>
>                 Key: HDFS-79
>                 URL: https://issues.apache.org/jira/browse/HDFS-79
>             Project: Hadoop HDFS
>          Issue Type: Bug
>         Environment: 17.0 + H1979-H2159-H3442
>            Reporter: Koji Noguchi
>            Priority: Minor
>
> Minor, but it would be nice if this exception is caught and logged.
> I see in .out file of datanode, 
> {noformat}
> Exception in thread "org.apache.hadoop.dfs.DataNode$DataTransfer@9d2805" java.nio.channels.ClosedSelectorException
>         at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:66)
>         at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:88)
>         at sun.nio.ch.Util.releaseTemporarySelector(Util.java:135)
>         at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:118)
>         at org.apache.hadoop.dfs.DataNode$DataTransfer.run(DataNode.java:2604)
>         at java.lang.Thread.run(Thread.java:619)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira