[
https://issues.apache.org/jira/browse/SOLR-18643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated SOLR-18643:
----------------------------------
Labels: pull-request-available (was: )
> SolrJ http2 client, allow clients to override pool properties
> -------------------------------------------------------------
>
> Key: SOLR-18643
> URL: https://issues.apache.org/jira/browse/SOLR-18643
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: Siju Varghese
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently pooled connections are reused for as long as they stay open; with
> HTTP/2 there are at most 4 per destination and no client idle timeout, so a
> degraded connection is never replaced. There is no way for a client to set
> any properties for this pool - max connections, idleTimeout, maxDuration etc.
> We are seeing issues in our env where degraded connections cause stalls and
> timeouts, with maxDuration setting in the pool there is a guarantee that such
> connections will be recycled at the specified frequency.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
