You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2022/07/19 21:07:00 UTC

[jira] [Assigned] (PHOENIX-6733) Ref count leaked test failures

     [ https://issues.apache.org/jira/browse/PHOENIX-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby reassigned PHOENIX-6733:
----------------------------------------

    Assignee: Geoffrey Jacoby

> 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
>            Assignee: 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)