[SOLR-16503] Switch UpdateShardHandler.getDefaultHttpClient to Jetty HTTP2

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: David Smiley
• Created: 27/Oct/22 16:22
• Updated: 6 days ago 03:52

Description

Much of Solr's remaining uses of Apache HttpClient (HTTP 1) is due to org.apache.solr.update.UpdateShardHandler#getDefaultHttpClient which underlies most Solr-to-Solr connectivity.  This also underlies the CoreContainer.getSolrClientCache.  Lets switch to Jetty (HTTP 2).

---

In SolrClientCache in particular:

Switch use of CloudLegacySolrClient.Builder to CloudSolrClient.Builder

Switch use of HttpSolrClient.Builder to Http2SolrClient.Builder

Undeprecate all the methods here.  They should not have been deprecated in the first place.

The constructor: switch from Apache HttpClient to a Jetty HttpClient.

Issue Links

• is a parent of: SOLR-17592 Apache->Jetty HttpClient for SolrCloudManager
• is a parent of: SOLR-17593 New CoreContainer.getDefaultHttpSolrClient (using Jetty HttpClient)
• is required by: SOLR-17286 HttpSolrCall.remoteQuery (proxy) should use Jetty HttpClient
• requires: SOLR-17538 CloudHttp2SolrClient needs a custom ClusterStateProvider option
• links to: GitHub Pull Request #2689
• links to: GitHub Pull Request #2741