[
https://issues.apache.org/jira/browse/PHOENIX-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562994#comment-17562994
]
Viraj Jasani commented on PHOENIX-6733:
---------------------------------------
I was also thinking about ParallelStats vs NeedsOwnCluster types and if the
leaks might be relevant, but when I looked at the last successful build on 5.1
branch, it was on 21st Mar, 2022
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/5.1/134/testReport/]
Perhaps that could be a starting point to see if we might have some commits
checked-in during this time period. The only problem is that now a days, these
test failures are not even flaky but rather consistent ones.
Similarly, for master branch, the last successful build was on 11th Jan, 2022
[https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-mulitbranch/job/master/375/]
which seems quite far away, so perhaps we could start chasing 5.1 branch first?
> Ref count leaked test failures
> ------------------------------
>
> Key: PHOENIX-6733
> URL: https://issues.apache.org/jira/browse/PHOENIX-6733
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.2.0
> Reporter: Geoffrey Jacoby
> Priority: Blocker
> Fix For: 5.2.0
>
>
> In pretty much every recent Yetus test run, some tests have flapped in the
> AfterClass teardown logic which tries to check for HBase Store reference
> resource leaks. The error message is "Ref count leaked", and some common
> suites this happens to are:
> DateTimeIT
> InListIT
> SequenceIT
> IndexToolForDeleteBeforeRebuildIT
> SpooledTmpFileDeleteIT
> I haven't had much luck trying to reproduce this locally. It's also not clear
> yet whether the root cause is an HBase error or a Phoenix one. (And if it's a
> Phoenix one, is the bug with something in Phoenix or with the resource
> check?)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
