[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077407#comment-17077407
]
Jacob Isaac commented on PHOENIX-5812:
--------------------------------------
[~dbwong] [~ckulkarni] [~liuml07] [~stoty]
Will need to keep PQS in mind too here
PQS does allow cached connections based on both size and last access time.
avatica.connectioncache.maxcapacity
avatica.connectioncache.expiryduration.
Also might be useful to define more crisply what does last accessed/interaction
time mean?
Do we need to track a long-running result iteration/mutation?
> Automatically Close "Idle" Long Open Connections
> ------------------------------------------------
>
> Key: PHOENIX-5812
> URL: https://issues.apache.org/jira/browse/PHOENIX-5812
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Daniel Wong
> Priority: Major
>
> As Phoenix may keep a maximum default number of connections. Badly
> performing client calls or internal errors (See PHOENIX-5802). Can cause
> total available connections to go to 0. Proposing a client connection
> monitor with a connection reaper like task to reap idle connections.
> Definition of "Idle"
> Simple may be simple time based say if a connection has been open for
> configurable amount of minutes simply close.
> More complicated solution may be keeping track of last interaction time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
