[
https://issues.apache.org/jira/browse/HDFS-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935566#comment-14935566
]
Hudson commented on HDFS-9141:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #434 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/434/])
HDFS-9141. Thread leak in Datanode#refreshVolumes. (Uma Maheswara Rao G via
yliu) (yliu: rev 715dbddf77866bb47a4b95421091f64a3785444f)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
> Thread leak in Datanode#refreshVolumes
> --------------------------------------
>
> Key: HDFS-9141
> URL: https://issues.apache.org/jira/browse/HDFS-9141
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 3.0.0, 2.7.1
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: 2.8.0
>
> Attachments: HDFS-9141.00.patch
>
>
> In refreshVolumes, we are creating executor service and submitting volume
> addition tasks to it.
> But we are not shutting down the service after the use. Even though we are
> not holding instance level service, the initialized thread could be left out.
> {code}
> ExecutorService service = Executors.newFixedThreadPool(
> changedVolumes.newLocations.size());
> {code}
> So, simple fix for this would be to shutdown the service after its use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
