[
https://issues.apache.org/jira/browse/PHOENIX-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15832763#comment-15832763
]
Hudson commented on PHOENIX-3611:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-master #1539 (See
[https://builds.apache.org/job/Phoenix-master/1539/])
PHOENIX-3611 Cache for client connections will expire (and close) (apurtell:
rev 9b7f3ca5b2e6bbf0757d99fbe48b3065e79d6066)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDriver.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
> ConnectionQueryService cache should expire LRU entries
> ------------------------------------------------------
>
> Key: PHOENIX-3611
> URL: https://issues.apache.org/jira/browse/PHOENIX-3611
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.8.0, 4.9.0
> Reporter: Geoffrey Jacoby
> Assignee: Geoffrey Jacoby
> Fix For: 4.10.0
>
> Attachments: PHOENIX-3611.patch, PHOENIX-3611-v2.patch
>
>
> Currently the cache of ConnectionInfo/ConnectionQueryServicesImpl can hold
> its entries forever. This can potentially lead to orphan cache entries, and
> since each ConnectionQueryServicesImpl object has an HConnection, it can also
> lead to leaked connections.
> Due to the way that ConnectionInfo hashing works (see PHOENIX-3126 and
> PHOENIX-3607), this is particularly likely on a secure cluster.
> The cache should be changed into an LRU-style cache with a fixed size and
> gradual expiration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
