[
https://issues.apache.org/jira/browse/SOLR-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17845181#comment-17845181
]
Mark Robert Miller commented on SOLR-16505:
-------------------------------------------
Yeah, probably. The idea was to isolate connection pools so that recovery
requests don’t have to queue up behind updates and queries and issues in one
type of pool don’t affect another - eg if connections are not fully read and
take a while to timeout frequently in the query pool, that won’t affect
recovery.
> Switch UpdateShardHandler.getRecoveryOnlyHttpClient to Jetty HTTP2
> ------------------------------------------------------------------
>
> Key: SOLR-16505
> URL: https://issues.apache.org/jira/browse/SOLR-16505
> Project: Solr
> Issue Type: Sub-task
> Reporter: David Smiley
> Priority: Major
> Time Spent: 8.5h
> Remaining Estimate: 0h
>
> This method and its callers (only RecoveryStrategy) should be converted to a
> Jetty HTTP2 client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
