[
https://issues.apache.org/jira/browse/PHOENIX-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022170#comment-16022170
]
Hudson commented on PHOENIX-3877:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-master #1620 (See
[https://builds.apache.org/job/Phoenix-master/1620/])
PHOENIX-3877 - Connection throttling doesn't always decrement on (gjacoby: rev
dfb2586aff0541fd596350823512500b86e932e1)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
* (edit)
phoenix-core/src/it/java/org/apache/phoenix/monitoring/PhoenixMetricsIT.java
> 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
> Fix For: 4.11.0
>
> 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)
