[
https://issues.apache.org/jira/browse/HDFS-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428985#comment-13428985
]
Todd Lipcon commented on HDFS-3754:
-----------------------------------
I'm a little confused, doesn't this have the same problem as before for tests?
i.e one DN shutting down will call ReadaheadPool.shutdown() on the only
instance, but anyone else who keeps a reference to that one will get exceptions
trying to submit to the executor?
Maybe we could fix this more easily by just changing the ReadaheadPool
ThreadFactory so that the threads don't get created inside any thread group?
Then they'd exit on JVM exit properly.
> 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
> Attachments: 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
