[
https://issues.apache.org/jira/browse/HDFS-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427553#comment-13427553
]
Todd Lipcon commented on HDFS-3754:
-----------------------------------
This doesn't look right. The ReadaheadPool is static. To fix this, I think you
need to either (a) move the ReadaheadPool inside the DN, and shut it down from
the DN context, (b) change the classloading of BlockSender so that the
ReadaheadPool doesn't get created inside the Datanode ThreadGroup, or (c) have
the DN shutdown method call something like
{{BlockSender.readaheadPool.shutdown()}}
> BlockSender doesn't shutdown ReadaheadPool threads
> --------------------------------------------------
>
> Key: HDFS-3754
> URL: https://issues.apache.org/jira/browse/HDFS-3754
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: data-node
> Affects Versions: 1.1.0, 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-3754.txt
>
>
> The BlockSender doesn't shutdown the ReadaheadPool threads so when tests are
> run with native libraries some tests fail (time out) because shutdown hangs
> waiting for the outstanding threads to exit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
