[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072317#comment-17072317
]
Daniel Wong commented on PHOENIX-5812:
--------------------------------------
Couple more thoughts after doing some additional research. Oracle provides a
connection lifetime parameter on the connection level. We could easily do that
and provide a default connection lifetime parameter default to infinite. I
think that gives the largest control to the end user, solves most lifetime
problems by configuring a default connection lifetime to a reasonable value.
We can look into concept of idle connections in a followup Jira if we decided
we wanted more complicated logic.
> 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)
