Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <960529823.1206427884280.JavaMail.jira@brutus>
Date: Mon, 24 Mar 2008 23:51:24 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3071) DFSOutputStream does not close all
 the sockets
In-Reply-To: <1601058612.1206139044443.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581795#action_12581795 ] 

dhruba borthakur commented on HADOOP-3071:
------------------------------------------

Code looks good. One question: the original code closes blockStream first and then close blockReplyStream. The new code closes blockReplyStream first. Is this on purpose?

> DFSOutputStream does not close all the sockets
> ----------------------------------------------
>
>                 Key: HADOOP-3071
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3071
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.17.0
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>         Attachments: HADOOP-3071.patch
>
>
> When DFSOutputStream writes to multiple blocks, it closes only the socket opened for the last block. When it is done with writing to one block it should close the socket.
> I noticed this when I was fixing HADOOP-3067. After fixing HADOOP-3067, there were still a lot of sockets open (but not enough to fail the tests). These sockets were used to write to blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.