phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3877) Connection throttling doesn't always decrement on connection close
Date Tue, 23 May 2017 23:41:04 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022096#comment-16022096
] 

James Taylor commented on PHOENIX-3877:
---------------------------------------

Don't forget 4.x-HBase-1.1 branch too please, [~gjacoby].

> 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)

Mime
View raw message