hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4326) Tests that use HBaseTestingUtility.startMiniCluster(n) should shutdown with HBaseTestingUtility.shutdownMiniCluster.
Date Mon, 05 Sep 2011 06:01:12 GMT

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

Jonathan Hsieh commented on HBASE-4326:
---------------------------------------

Hm.. looks like this actually done, but apache jenkins truncates the data so that it is not
available from the build's logs.  I've noticed some similar flaky test failures on my side
and will do some runs to try to duplicate failures and  that keeps the full stdout/logs so
we can debug.

> Tests that use HBaseTestingUtility.startMiniCluster(n) should shutdown with HBaseTestingUtility.shutdownMiniCluster.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4326
>                 URL: https://issues.apache.org/jira/browse/HBASE-4326
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4
>            Reporter: Jonathan Hsieh
>
> Most tests that use mini clusters use this pattern
> {code}
>  private final static HBaseTestingUtility UTIL = new HBaseTestingUtility();
>   @BeforeClass
>   public static void beforeClass() throws Exception {
>     UTIL.startMiniCluster(1);
>   }
>   @AfterClass
>   public static void afterClass() throws IOException {
>     UTIL.shutdownMiniCluster();
>   }
> {code}
> Some tests (like hbase-4269)
> {code}
>   @BeforeClass
>   public static void beforeClass() throws Exception {
>     UTIL.startMiniCluster(1);
>   }
>   @AfterClass
>   public static void afterClass() throws IOException {
>     UTIL.getMiniCluster().shutdown();
>     // or UTIL.shutdownMiniHBaseCluster();
>     // and likely others.
>   }
> {code}
> There is a difference between the two shutdown -- the former deletes files created during
the tests while the latter does not.  This funny state persisting (zk or hbase/mr data) may
be the cause of strange inter-testcase problems when full suites are run.

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

        

Mime
View raw message