FAQ
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

Search Discussions

  • Suresh Srinivas (JIRA) at Jun 10, 2011 at 12:48 am
    [ https://issues.apache.org/jira/browse/HDFS-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Suresh Srinivas resolved HDFS-2057.
    -----------------------------------

    Resolution: Fixed
    Hadoop Flags: [Reviewed]

    I committed the patch to 204, 205 and branch-0.20-security. Thank you Bharath.
    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

    Attachments: HDFS-2057-1.patch


    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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouphdfs-dev @
categorieshadoop
postedJun 10, '11 at 12:10a
activeJun 10, '11 at 12:48a
posts2
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Suresh Srinivas (JIRA): 2 posts

People

Translate

site design / logo © 2022 Grokbase