phoenix-dev mailing list archives

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

             Summary: 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


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