Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1CD9C77F0 for ; Mon, 24 Oct 2011 18:20:55 +0000 (UTC) Received: (qmail 82583 invoked by uid 500); 24 Oct 2011 18:20:55 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 82517 invoked by uid 500); 24 Oct 2011 18:20:54 -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 82509 invoked by uid 99); 24 Oct 2011 18:20:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Oct 2011 18:20:54 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Oct 2011 18:20:52 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 5F141319A15 for ; Mon, 24 Oct 2011 18:18:32 +0000 (UTC) Date: Mon, 24 Oct 2011 18:18:32 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (Updated) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <442455977.9737.1319480312390.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <798053698.6804.1319387432133.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HDFS-2494) [webhdfs] When Getting the file using OP=OPEN with DN http address, ESTABLISHED sockets are growing. 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-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-2494: ----------------------------------------- Attachment: h2494_20111024.patch Hi Uma, thanks for catching the bug. The input stream is not closed in the case {{n == null}}. The two {{IOUtils.copyBytes(..}}}s behave differently: the second one closes in but the first does not. h2494_20111024.patch: close in. Could you test the patch? > [webhdfs] When Getting the file using OP=OPEN with DN http address, ESTABLISHED sockets are growing. > ---------------------------------------------------------------------------------------------------- > > Key: HDFS-2494 > URL: https://issues.apache.org/jira/browse/HDFS-2494 > Project: Hadoop HDFS > Issue Type: Bug > Components: data-node > Affects Versions: 0.24.0 > Reporter: Uma Maheswara Rao G > Assignee: Uma Maheswara Rao G > Attachments: h2494_20111024.patch > > > As part of the reliable test, > Scenario: > Initially check the socket count. ---there are aroud 42 sockets are there. > open the file with DataNode http address using op=OPEN request parameter about 500 times in loop. > Wait for some time and check the socket count. --- There are thousands of ESTABLISHED sockets are growing. ~2052 > Here is the netstat result: > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > C:\Users\uma>netstat | grep 127.0.0.1 | grep ESTABLISHED |wc -l > 2042 > This count is not coming down. -- 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