[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080309#comment-17080309
]
Mingliang Liu commented on PHOENIX-5812:
----------------------------------------
Thanks [~elserj] Yes both two problems will be resolved if we clean up those
idle PConnections. When an idle PConnection is detected and closed by this
monitor thread, the connection count will be decreased so throttling problem
will be gone. Meanwhile, the renew lease task scheduled periodically will
remove a closed PConnection from connection queue in CQSI eventually. My major
concern is it requires advanced implementation to make closing PConnection
least user facing. Glad the above idea seems OK.
So with this JIRA, do we design and implement solutions like that, or we target
the basic closing first (which is the last item only in the above 4 points)?
Thoughts? [~dbwong] [~ckulkarni] [~pawan.prakash]
> 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)
