Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 33833 invoked from network); 30 Dec 2010 11:24:11 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Dec 2010 11:24:11 -0000 Received: (qmail 69406 invoked by uid 500); 30 Dec 2010 11:24:11 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 69305 invoked by uid 500); 30 Dec 2010 11:24:10 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 69297 invoked by uid 99); 30 Dec 2010 11:24:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Dec 2010 11:24:10 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Dec 2010 11:24:07 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oBUBNkH0029394 for ; Thu, 30 Dec 2010 11:23:46 GMT Message-ID: <1949424.70271293708226321.JavaMail.jira@thor> Date: Thu, 30 Dec 2010 06:23:46 -0500 (EST) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-1540) Make Datanode handle errors to namenode.register call more elegantly In-Reply-To: <14580471.149031292460182236.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976014#action_12976014 ] Hadoop QA commented on HDFS-1540: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12467161/datanodeException5.txt against trunk revision 1053214. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these core unit tests: org.apache.hadoop.hdfs.server.namenode.TestStorageRestore org.apache.hadoop.hdfs.TestFileConcurrentReader -1 contrib tests. The patch failed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/60//testReport/ Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/60//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/60//console This message is automatically generated. > 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 > Components: data-node > Affects Versions: 0.20.1, 0.20.2, 0.21.0 > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Fix For: 0.23.0 > > Attachments: datanodeException1.txt, datanodeException2.txt, datanodeException3.txt, datanodeException4.txt, datanodeException5.txt, datanodeException5.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.