[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079564#comment-17079564
]
Josh Elser commented on PHOENIX-5812:
-------------------------------------
bq. Since this was related PHOENIX-5802, assumed it was related to
PhoenixConnections and not the underlying HConnections in CQSI.
Yeah, sorry if I have been derailing. Maybe I am not understanding how
PhoenixConnections have some ability to leak and cause problems. My assumption
was that, since PConn's are cheap and don't represent any real open
sockets/connections, we were really concerned about being able to shut down the
CQSI/HConn. Sorry if I've been detracting :)
> 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)
