[
https://issues.apache.org/jira/browse/HDFS-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430837#comment-13430837
]
Eli Collins commented on HDFS-3754:
-----------------------------------
Forgot to mention, in this case DataXceiverServer is creating the threads and
it has the ThreadGroup that the DN is checking the count against which is why
we don't want threads created with this ThreadGroup, and logically the
ReadaHead thread pool doesn't need to share a group with the dataXceiverServer
threads.
> 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.2.0, 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: 2.2.0-alpha
>
> Attachments: hdfs-3754-b1.txt, hdfs-3754-b1.txt, hdfs-3754.txt,
> hdfs-3754.txt, hdfs-3754.txt, hdfs-3754.txt, hdfs-3754.txt, hdfs-3754.txt,
> 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
