[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072251#comment-17072251
]
Mingliang Liu commented on PHOENIX-5812:
----------------------------------------
I like this feature, and can work on this and relative tasks if it's well
defined. Is it worth to split the work to separate threshold: soft and hard?
The ones whose last interaction time / open time is larger than soft threshold
will be reported/logged as "idle-ness". The ones whose last interaction time /
open time is larger than hard threshold will be closed. The default soft
threshold is 1 day and the default hard threshold is LONG.MAX_VALUE. Will this
address the "destructive" concern?
> 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)
