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-9612) DistCp worker threads are not terminated after jobs are done.
Date Fri, 15 Jan 2016 18:35:39 GMT

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

Hudson commented on HDFS-9612:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #9121 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9121/])
HDFS-9612. DistCp worker threads are not terminated after jobs are done. (yzhang: rev a9c69ebeb707801071db3cc22bfcd14f87be443a)
* hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/util/WorkRequestProcessor.java
* hadoop-tools/hadoop-distcp/src/test/java/org/apache/hadoop/tools/util/TestProducerConsumer.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-tools/hadoop-distcp/src/main/java/org/apache/hadoop/tools/util/ProducerConsumer.java


> DistCp worker threads are not terminated after jobs are done.
> -------------------------------------------------------------
>
>                 Key: HDFS-9612
>                 URL: https://issues.apache.org/jira/browse/HDFS-9612
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: distcp
>    Affects Versions: 2.8.0
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
>         Attachments: HDFS-9612.001.patch, HDFS-9612.002.patch, HDFS-9612.003.patch, HDFS-9612.004.patch,
HDFS-9612.005.patch, HDFS-9612.006.patch, HDFS-9612.007.patch, HDFS-9612.008.patch, HDFS-9612.009.patch
>
>
> In HADOOP-11827, a producer-consumer style thread pool was introduced to parallelize
the task of listing files/directories.
> We have a use case where a distcp job is run during the commit phase of a MR2 job. However,
it was found distcp does not terminate ProducerConsumer thread pools properly. Because threads
are not terminated, those MR2 jobs never finish.
> In a more typical use case where distcp is run as a standalone job, those threads are
terminated forcefully when the java process is terminated. So these leaked threads did not
become a problem.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message