[
https://issues.apache.org/jira/browse/PHOENIX-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568667#comment-17568667
]
Geoffrey Jacoby commented on PHOENIX-6733:
------------------------------------------
I checked the logging from the store ref check, and found that in the couple of
examples I looked at it was always hbase:meta that was the region leaking.
Since it's totally fine for some background process in a minicluster to be
reading meta, I'm going to push up a PR with meta skipped in the check to see
if that clears up the test failures.
If not we may need to similarly exempt SYSTEM.CATALOG and SYSTEM.TASK.
> 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)
