phoenix-issues mailing list archives

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

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

Hudson commented on PHOENIX-5311:
---------------------------------

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #416 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/416/])
PHOENIX-5311 Fix distributed cluster test resource (hbase table) leak (chinmayskulkarni: rev
5c49fd54725a77b8f3540e610b49ba46d874916d)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsDisabledIT.java
* (edit) phoenix-core/src/test/java/org/apache/phoenix/query/BaseTest.java
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/ParallelStatsEnabledIT.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)

Mime
View raw message