hadoop-hdfs-issues mailing list archives

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

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

Konstantin Shvachko commented on HDFS-1540:
-------------------------------------------

A nit. Would you use {{LOG.info(msg, e)}} instead of {{stringifyException}}. It really looks
better in the logs that way.
The rest looks good to me.
+1

Could you please fill the missing jira fields (versions, components).


> 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, datanodeException2.txt, datanodeException3.txt,
datanodeException4.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.


Mime
View raw message