Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Fri, 10 Jun 2011 00:09:58 +0000 (UTC)
From: "Bharath Mundlapudi (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <209544385.9193.1307664598931.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-2057) Wait time to terminate the threads
 causing unit tests to take longer time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Wait time to terminate the threads causing unit tests to take longer time
-------------------------------------------------------------------------

                 Key: HDFS-2057
                 URL: https://issues.apache.org/jira/browse/HDFS-2057
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: data-node
    Affects Versions: 0.20.204.0, 0.20.205.0
            Reporter: Bharath Mundlapudi
            Assignee: Bharath Mundlapudi
             Fix For: 0.20.205.0


As a part of datanode process hang, this part of code was introduced in 0.20.204 to clean up all the waiting threads.

-      try {
-          readPool.awaitTermination(10, TimeUnit.SECONDS);
-      } catch (InterruptedException e) {
-       LOG.info("Exception occured in doStop:" + e.getMessage());
-      }
-      readPool.shutdownNow();

This was clearly meant for production, but all the unit tests uses minidfscluster and minimrcluster for shutdown which waits on this part of the code. Due to this, we saw increase in unit test run times. So removing this code. 


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira