You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Daniel Wong (Jira)" <ji...@apache.org> on 2021/11/09 21:44:00 UTC
[jira] [Commented] (PHOENIX-6549) Connection leak checks sometimes
fail in tests
[ https://issues.apache.org/jira/browse/PHOENIX-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441379#comment-17441379 ]
Daniel Wong commented on PHOENIX-6549:
--------------------------------------
Certain paths use both, for specifically upsert-select and delete we should test internal and non-internal. We should likely handle both.
> Connection leak checks sometimes fail in tests
> ----------------------------------------------
>
> Key: PHOENIX-6549
> URL: https://issues.apache.org/jira/browse/PHOENIX-6549
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.2.0
> Reporter: Istvan Toth
> Priority: Major
> Attachments: org.apache.phoenix.end2end.UpsertSelectIT-output.txt.bz2, org.apache.phoenix.end2end.UpsertSelectIT.txt.gz
>
>
> In rare cases we see
> {code:java}
> GLOBAL_OPEN_PHOENIX_CONNECTIONS.getMetric().getValue()
> {code}
> returning 1 instead of 0, even thugh the test class uses try-with-resources blocks to handle the Phoenix Connections.
> I'm attaching the output from a recent test run on ASF Jenkins
--
This message was sent by Atlassian Jira
(v8.20.1#820001)