hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1540) Make Datanode handle errors to namenode.register call more elegantly
Date Tue, 28 Dec 2010 00:06:46 GMT

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

Todd Lipcon commented on HDFS-1540:

Hi Dhruba. I'm a little confused by this patch. When can versionRequest throw exceptions like
UnregisteredNodeException or DisallowedDatanodeException? These exceptions are thrown by registerDatanode,
not by versionRequest.

I think maybe we should just widen SocketTimeoutException to IOException overall?

> Make Datanode handle errors to namenode.register call more elegantly
> --------------------------------------------------------------------
>                 Key: HDFS-1540
>                 URL: https://issues.apache.org/jira/browse/HDFS-1540
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: datanodeException1.txt
> When a datanode receives a "Connection reset by peer" from the namenode.register(), it
exits. This causes many datanodes to die.

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

View raw message