[
https://issues.apache.org/jira/browse/PHOENIX-6549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416577#comment-17416577
]
Viraj Jasani commented on PHOENIX-6549:
---------------------------------------
[~dbwong] FYI. Do you think we should use
"GLOBAL_OPEN_INTERNAL_PHOENIX_CONNECTIONS" instead of
"GLOBAL_OPEN_PHOENIX_CONNECTIONS" ? Was just looking into this logic and
wondering if internal connections are the ones we should focus on in
UpsertSelectIT tests.
{code:java}
if(isInternalConnection) {
GLOBAL_OPEN_INTERNAL_PHOENIX_CONNECTIONS.increment();
} else {
GLOBAL_OPEN_PHOENIX_CONNECTIONS.increment();
}
{code}
> 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.3.4#803005)
