hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3754) BlockSender doesn't shutdown ReadaheadPool threads
Date Mon, 06 Aug 2012 23:03:04 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429552#comment-13429552
] 

Colin Patrick McCabe commented on HDFS-3754:
--------------------------------------------

Initializing the ReadaheadPool in DataNode seems like a good idea to me.  I also tested the
latest patch, and it worked for me.

Would it be worthwhile to add a comment to ReadaheadPool about the importance of having the
correct thread context?  Or maybe just a reference to this JIRA.  I know that I definitely
wouldn't have considered the importance of thread context in this situation.
                
> 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

        

Mime
View raw message