[
https://issues.apache.org/jira/browse/PHOENIX-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074834#comment-17074834
]
Daniel Wong commented on PHOENIX-5812:
--------------------------------------
If we want to do idleness correctly the first time we certainly can; however,
there is value to the timing since connection open since for our usecases our
customers use we expect no connection to be used for multiple queries due to
the lightweight nature of our connections and our communicated recommended call
pattern.
>From the monitor vs doing this at throttle time. I slightly prefer doing it
>as a monitor as this would hopefully make the OPEN_CONNECTIONS metric clearer.
> And two the end user experience. If they hit a throttled event we could do 2
>paths, 1 retry the query internally after calling `closeAllIdleConnections()`.
> Two have the end user retry. Both add latency retries that I would want to
>avoid.
Any thoughts from outside of Salesforce? [~elserj] [~stoty] [~RichardAntal]
[~vtpavan]
> 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)
