[
https://issues.apache.org/jira/browse/PHOENIX-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858214#comment-16858214
]
Hudson commented on PHOENIX-5311:
---------------------------------
FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #2632 (See
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/2632/])
PHOENIX-5311 Fix distributed cluster test resource (hbase table) leak
(chinmayskulkarni: rev 5303d292a4c875f8ee8f484094c897f8e7595e63)
* (edit) phoenix-core/src/test/java/org/apache/phoenix/query/BaseTest.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsEnabledIT.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsDisabledIT.java
> Integration tests leak tables when running on distributed cluster
> -----------------------------------------------------------------
>
> Key: PHOENIX-5311
> URL: https://issues.apache.org/jira/browse/PHOENIX-5311
> 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
(v7.6.3#76005)
