You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/03/22 02:01:26 UTC
[jira] Commented: (HADOOP-3071) DFSOutputStream does not close all
the sockets
[ https://issues.apache.org/jira/browse/HADOOP-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581230#action_12581230 ]
Raghu Angadi commented on HADOOP-3071:
--------------------------------------
This does not affect 0.16. Closing s.getOutputStream() also closes the socket (not just the otherway round). o.a.h.SocketOutputStream() should do the same. But still I think patch is good as it is.. it cleans up the code a bit and closes the socket if connection fails inside createBlockOutputStream().
> 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
> Fix For: 0.17.0
>
> 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.