phoenix-issues mailing list archives

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


Hudson commented on PHOENIX-5311:

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.5 #16 (See [])
PHOENIX-5311 Fix distributed cluster test resource (hbase table) leak (chinmayskulkarni: rev
* (edit) phoenix-core/src/test/java/org/apache/phoenix/query/
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/

> Integration tests leak tables when running on distributed cluster
> -----------------------------------------------------------------
>                 Key: PHOENIX-5311
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: István Tóth
>            Assignee: 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