[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076105#comment-17076105
]
Richard Antal commented on PHOENIX-5812:
----------------------------------------
My suggestion would be to create some kind of priority queue based on the last
interaction time. When the available connections are 0 we should drop the least
active connection from the queue.
This way we wouldn't close "idle" connections unnecessary when the load is
light.
I think it is important to take account in the actual load on phoenix server,
it would be hard to make up a good time out parameter.
{quote}suggest that the improvement be as least-user-facing as possible
{quote}
+1
> 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)
