phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-5311) Integration tests leak tables when running on distributed cluster
Date Thu, 06 Jun 2019 13:00:00 GMT


Hadoop QA commented on PHOENIX-5311:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit 27bc7140de826929fdad4c4027b609dc20b0dbe3.
  ATTACHMENT ID: 12971048

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 release audit{color}.  The applied patch generated 2 release audit warnings
(more than the master's current 0 warnings).

    {color:red}-1 lineLengths{color}.  The patch introduces the following lines longer than
    +                        "Deleting old tables on distributed cluster because number of
tables is likely greater than "
+                    "Shutting down mini cluster because number of tables on this mini cluster
is likely greater than "

     {color:red}-1 core tests{color}.  The patch failed these unit tests:

Test results:
Release audit warnings:
Console output:

This message is automatically generated.

> Integration tests leak tables when running on distributed cluster
> -----------------------------------------------------------------
>                 Key: PHOENIX-5311
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: István Tóth
>            Priority: Major
>         Attachments: PHOENIX-5311.master.v1.patch
> When integration test suite is run via End2EndTestDriver on a distributed cluster, most
tests do not clean up their tables, leaving thousands of tables on the cluster, and exhausting
RegionServer memory.
> There are actually three problems:
>  * The BaseTest.freeResourcesIfBeyondThreshold() method is called after most tests, and
it restarts the MiniCluster, thus freeing resources, but it has no effect when running on
a distributed cluster.
>  * The TestDriver sets phoenix.schema.dropMetaData to false by default, so even if the
Phoenix tables are dropped, the HBASE tables are not, so the table leak remains. 
>  * The phoenix.schema.dropMetaData setting cannot be easily overridden because of PHOENIX-5310

This message was sent by Atlassian JIRA

View raw message