hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5493) DFSClient#DFSInputStream#blockSeekTo may leak socket connection.
Date Wed, 13 Nov 2013 08:37:18 GMT

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

Hadoop QA commented on HDFS-5493:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12613530/HDFS-5493-branch-1.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5418//console

This message is automatically generated.

> DFSClient#DFSInputStream#blockSeekTo may leak socket connection.
> ----------------------------------------------------------------
>
>                 Key: HDFS-5493
>                 URL: https://issues.apache.org/jira/browse/HDFS-5493
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 1.2.1
>            Reporter: Chris Nauroth
>         Attachments: HDFS-5493-branch-1.patch
>
>
> {{DFSClient#DFSInputStream#blockSeekTo}} may handle {{IOException}} by refetching a new
block access token and then reattempting {{fetchBlockAt}}.  However, {{fetchBlockAt}} may
then throw its own {{IOException}}.  If this happens, then the method skips calling {{Socket#close}}.
 This is likely to manifest as a leak of sockets left in CLOSE_WAIT status.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message