[
https://issues.apache.org/jira/browse/PHOENIX-5801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068286#comment-17068286
]
Chinmay Kulkarni commented on PHOENIX-5801:
-------------------------------------------
[~gjacoby] Good point. I was actually checking the
GLOBAL_OPEN_PHOENIX_CONNECTIONS metric value, rather than the connectionCount
which is incremented on addConnection only for CQSI (not CLQSI).
I basically came across this when adding an "After" method in an IT which made
sure there were no Phoenix connections kept open after each test. Let me modify
the Jira description. As you mentioned, we should close the connection anyway
since it would unnecessarily contribute to the open connections metric.
> Connection leak when creating a view with a where condition
> -----------------------------------------------------------
>
> Key: PHOENIX-5801
> URL: https://issues.apache.org/jira/browse/PHOENIX-5801
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Chinmay Kulkarni
> Assignee: Chinmay Kulkarni
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5801-4.x-v1.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When you create a view with a where condition, we open a connection-less
> Phoenix connection, which is never closed. This is a connection leak which
> reduces available connections for end-clients when throttling is enabled,
> amongst other problems, so we should close the connection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
