You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2020/06/16 16:57:02 UTC
[jira] [Commented] (PHOENIX-5730) Stabilize tests on master branch
[ https://issues.apache.org/jira/browse/PHOENIX-5730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136818#comment-17136818 ]
Chinmay Kulkarni commented on PHOENIX-5730:
-------------------------------------------
FYI [~neha.gupta] [~sandeep.guggilam] some of this work may be related to the Master not initialized work you both have been looking into
> Stabilize tests on master branch
> --------------------------------
>
> Key: PHOENIX-5730
> URL: https://issues.apache.org/jira/browse/PHOENIX-5730
> Project: Phoenix
> Issue Type: Task
> Reporter: Istvan Toth
> Priority: Major
> Labels: phoenix-hardening, quality-improvement
>
> There are frequent integration test failures on the master branch, that have no apparent rhyme or reason.
> Most of the failures seem to be related to timeouts, and performance issues.
> The failures seem more frequent when testing against the HBase 2.1 and HBase 2.2 profiles.
> Investigate the causes, and try to stabilise the tests.
> Some ideas to start with:
> * Try to copy the performance related minicluster settings from the integration tests in the 2.2 HBase branchÂ
> * investigate the test execution times to see whether and where there is a correlation between execution time increases and HBase profiles.
> * Investigate whether the failing tests have execution times that are close to the timeout values during successful runs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)