hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4161) HDFS keeps a thread open for every file writer
Date Thu, 08 Nov 2012 20:48:12 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-4161:

test-patch results:
     [exec] -1 overall.  
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 21 new or modified tests.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     -1 findbugs.  The patch appears to introduce 9 new Findbugs (version 1.3.9)
> HDFS keeps a thread open for every file writer
> ----------------------------------------------
>                 Key: HDFS-4161
>                 URL: https://issues.apache.org/jira/browse/HDFS-4161
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 1.0.0
>            Reporter: Suresh Srinivas
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: h4161_20121108_b-1.patch
> In 1.0 release DFSClient uses a thread per file writer. In some use cases (dynamic partions
in hive) that use a large number of file writers a large number of threads are created. The
file writer thread has the following stack:
> {noformat}
> at java.lang.Thread.sleep(Native Method)
> at org.apache.hadoop.hdfs.DFSClient$LeaseChecker.run(DFSClient.java:1462)
> at java.lang.Thread.run(Thread.java:662)
> {noformat}
> This problem has been fixed in later releases. This jira will post a consolidated patch
from various jiras that addresses the issue.

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

View raw message