Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sat, 4 Aug 2012 00:15:02 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <277392353.12694.1344039302742.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <678227907.6384.1343928483114.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HDFS-3754) BlockSender doesn't shutdown
 ReadaheadPool threads
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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

Yea, I think moving the ReadaheadPool intialization and shutdown to the DN makes more sense after all. 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
>
>
> 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