Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 84702 invoked from network); 8 Mar 2008 20:15:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Mar 2008 20:15:10 -0000 Received: (qmail 57398 invoked by uid 500); 8 Mar 2008 20:15:05 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 57368 invoked by uid 500); 8 Mar 2008 20:15:05 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 57359 invoked by uid 99); 8 Mar 2008 20:15:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Mar 2008 12:15:05 -0800 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.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 08 Mar 2008 20:14:26 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 32E47234C08A for ; Sat, 8 Mar 2008 12:13:46 -0800 (PST) Message-ID: <979776354.1205007226207.JavaMail.jira@brutus> Date: Sat, 8 Mar 2008 12:13:46 -0800 (PST) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-2870) Datanode.shutdown() and Namenode.stop() should close all rpc connections In-Reply-To: <1889284436.1203629959313.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576602#action_12576602 ] Hadoop QA commented on HADOOP-2870: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12377394/closeConnection4.patch against trunk revision 619744. @author +1. The patch does not contain any @author tags. tests included +1. The patch appears to include 12 new or modified tests. javadoc +1. The javadoc tool did not generate any warning messages. javac +1. The applied patch does not generate any new javac compiler warnings. release audit +1. The applied patch does not generate any new release audit warnings. findbugs +1. The patch does not introduce any new Findbugs warnings. core tests +1. The patch passed core unit tests. contrib tests +1. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1916/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1916/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1916/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1916/console This message is automatically generated. > Datanode.shutdown() and Namenode.stop() should close all rpc connections > ------------------------------------------------------------------------ > > Key: HADOOP-2870 > URL: https://issues.apache.org/jira/browse/HADOOP-2870 > Project: Hadoop Core > Issue Type: Bug > Components: ipc > Affects Versions: 0.16.0 > Reporter: Hairong Kuang > Assignee: Hairong Kuang > Fix For: 0.17.0 > > Attachments: closeConnection.patch, closeConnection1.patch, closeConnection2.patch, closeConnection3.patch, closeConnection4.patch > > > Currently this two cleanup methods do not close all existing rpc connections. If a mini dfs cluster gets shutdown and then restarted as we do in TestFileCreation, RPCs in second mini cluster reuse the unclosed connections opened in the first run but there is no server running to serve the request. So the client get stuck waiting for the response forever if client side timeout gets removed as suggested by hadoop-2811. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.