[
https://issues.apache.org/jira/browse/HDFS-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HDFS-3754:
------------------------------
Attachment: hdfs-3754.txt
Good point, it's possible in a test that an existing active block sender could
race with the shutdown of another DN and submit to the pool that's been
shutdown.
I like the idea making the ReadaheadPool pool not part of the dataXceiverServer
thread group, this can actually be accomplished more easily by just moving the
initialization from BlockSender to DataNode, which is a more logical place
anyway. Updated patch attached.
> 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, 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
