[SOLR-16367] Umbrella: Migrate away from Apache HttpClient.

• Type: Improvement
• Status: Open
• Priority: Blocker
• Resolution: Unresolved
• Fix Version/s: main (10.0)
• Assignee: Unassigned
• Reporter: David Smiley
• Created: 01/Sep/22 13:37
• Updated: 31/Oct/24 19:23

Description

This is an umbrella issue to migrate away from using Apache HttpClient to alternatives, namely Jetty HttpClient. Supporting both is hard to maintain, and furthermore Jetty supports HTTP 2. Sub-tasks and linked issues will accomplish this. When this umbrella is done, Apache HttpClient will not be used in solr-core or solrj. Modules may use it only if required by dependencies. HttpSolrClient (which uses Apache HttpClient) can still exist but in its own opt-in SolrJ module.

Issue Links

• relates to: SOLR-15223 Deprecate Apache-HttpClient, refactor CloudSolrClient to use jetty-httpclient
• relates to: SOLR-17201 Make Http2SolrClients not experimental
• relates to: SOLR-16498 Tests need the URL from a SolrClient; don't require legacy clients
• requires: SOLR-17538 CloudHttp2SolrClient needs a custom ClusterStateProvider option
• requires: SOLR-16368 Refactoring: Use SolrClient type instead of overly specific subclasses

Sub-Tasks

• Convert CLI tools to Jetty HTTP 2 client.: Closed
• Switch UpdateShardHandler.getRecoveryOnlyHttpClient to Jetty HTTP2: Closed
• Switch UpdateShardHandler.getDefaultHttpClient to Jetty HTTP2: Open
• Allow SolrClientCache clients to use Jetty HTTP2 clients: Closed
• Update IndexFetcher Class to Use Http2SolrClient: Resolved
• Move RemoteSolrException to SolrClient in v10: Resolved
• HttpSolrCall.remoteQuery (proxy) should use Jetty HttpClient: Open
• Update SyncStrategy and PeerSyncWithLeader to use the recovery Http2SolrClient: Closed
• Copy existing listeners on re-creation of Http2SolrClient: Closed