Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 2 Sep 2011 22:10:10 +0000 (UTC)
From: "Suresh Srinivas (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1014190081.12964.1315001410254.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1118) DFSOutputStream socket leak when
 cannot connect to DataNode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Suresh Srinivas commented on HDFS-1118:
---------------------------------------

I have committed the patch to 0.20-security branch.

> DFSOutputStream socket leak when cannot connect to DataNode
> -----------------------------------------------------------
>
>                 Key: HDFS-1118
>                 URL: https://issues.apache.org/jira/browse/HDFS-1118
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.20.1, 0.20.2, 0.20-append, 0.21.0
>            Reporter: Zheng Shao
>            Assignee: Zheng Shao
>             Fix For: 0.20-append, 0.20.205.0, 0.22.0
>
>         Attachments: HDFS-1118.1.patch, HDFS-1118.2.patch, hdfs-1118.20s.patch, trunkPatch.txt
>
>
> The offending code is in {{DFSOutputStream.nextBlockOutputStream}}
> This function retries several times to call {{createBlockOutputStream}}. Each time when it fails, it leaves a {{Socket}} object in {{DFSOutputStream.s}}.
> That object is never closed, but overwritten the next time {{createBlockOutputStream}} is called.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira