[
https://issues.apache.org/jira/browse/PHOENIX-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021972#comment-16021972
]
Geoffrey Jacoby commented on PHOENIX-3877:
------------------------------------------
The release audit warning is unrelated to this change and is fixed by
PHOENIX-3877. Not sure why there's a -1 to tests included, because I altered
PhoenixMetricsIT to capture the use case this patch fixes. I ran the failing
TransactionalViewIT locally and it passes.
> Connection throttling doesn't always decrement on connection close
> ------------------------------------------------------------------
>
> Key: PHOENIX-3877
> URL: https://issues.apache.org/jira/browse/PHOENIX-3877
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.10.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Attachments: PHOENIX-3877.patch
>
>
> PHOENIX-3663 introduced optional connection throttling in the JDBC driver.
> While the throttling itself works properly, the decrement operation on
> connection close won't update the open connection count unless an unrelated
> setting, returnSequenceValues, is true. (This is because the connection
> counts were originally built for sequence logic.) The result is that once we
> throttle, we often can't un-throttle even after congestion abates.
> The decrement operation on connection close should also take place anytime
> the connection throttling is turned on.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
