[
https://issues.apache.org/jira/browse/PHOENIX-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Buzsaki updated PHOENIX-1099:
----------------------------------
Attachment: PHOENIX-1099.patch
Attached is a fix for this issue, renaming and reannotating the test class so
that it is properly run at integration test time and not unit test time.
> Fix performance issues with unit tests.
> ---------------------------------------
>
> Key: PHOENIX-1099
> URL: https://issues.apache.org/jira/browse/PHOENIX-1099
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Kyle Buzsaki
> Assignee: rajeshbabu
> Labels: performance
> Attachments: PHOENIX-1099.patch
>
>
> After commit 247ac8eee8ca604ca1616ba4bcf91fec6475ea88, the unit test suite
> run by mvn test started taking a very long time to run.
> Prior to that commit, running the unit test suite would take around 15-20
> seconds. After that commit and for every commit afterwards the unit tests
> appear to hang at the last test and take 1:45-2:00 to complete.
> Addendum: looks like the culprit is
> org.apache.phoenix.hbase.index.balancer.TestIndexLoadBalancer. This class is
> run with the unit tests but it spins up and shuts down an HBase mini-cluster.
> Commenting out the body of the class fixes the performance issue. Seems like
> this should be an Integration Test, not a Unit Test. Was that the intention?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
