hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4768) File handle leak in datanode when a block pool is removed
Date Sun, 28 Apr 2013 14:08:18 GMT

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

Hudson commented on HDFS-4768:
------------------------------

Integrated in Hadoop-Mapreduce-trunk #1413 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1413/])
    HDFS-4768. File handle leak in datanode when a block pool is removed. Contributed by Chris
Nauroth. (Revision 1476579)

     Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1476579
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataBlockScanner.java

                
> File handle leak in datanode when a block pool is removed
> ---------------------------------------------------------
>
>                 Key: HDFS-4768
>                 URL: https://issues.apache.org/jira/browse/HDFS-4768
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>    Affects Versions: 3.0.0, 2.0.4-alpha
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 2.0.5-beta
>
>         Attachments: HDFS-4768.1.patch
>
>
> HDFS-4274 fixed a file handle leak of the block scanner's verification logs by adding
method {{BlockPoolSliceScanner#shutdown}} and guaranteeing that the method gets called for
each live {{BlockPoolSliceScanner}} during datanode shutdown.  However, that patch did not
consider the case of deleting a block pool via {{ClientDatanodeProtocol#deleteBlockPool}}
while the datanode remains running.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message