[
https://issues.apache.org/jira/browse/SOLR-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496208#comment-16496208
]
Mark Miller commented on SOLR-12297:
------------------------------------
Just give me a short bit to ignore the rest of the currently failing tests so
that we can have a clean test run as a base and then I'll move it over to an
Apache branch.
I'll make a new issue to track and discuss the overall objective.
This issue will be about Jetty HttpClient and Http2SolrClient.
I split out HTTP/2 to SOLR-12404 Start using HTTP/2 instead of HTTP/1.1.
SOLR-12405 is for request throttling / dropping.
There are other issues that can be pulled out - stop using sleeps for example,
clean up thread usage, clean up resource usage, add tests and enforcers to
keeps things in shape, etc.
HTTP/2 is probably the most work to finish, along with full Jetty HttpClient
usage. We can keep using Apache HttpClient and add Http2SolrClient powered by
Jetty HttpClient against HTTP/1.1 if we want though.
> Create a good SolrClient for SolrCloud paving the way for async requests,
> HTTP2, multiplexing, and the latest & greatest Jetty features.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-12297
> URL: https://issues.apache.org/jira/browse/SOLR-12297
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
>
> Blocking or async support as well as HTTP2 compatible with multiplexing.
> Once it supports enough and is stable, replace internal usage, allowing
> async, and eventually move to HTTP2 connector and allow multiplexing. Could
> support HTTP1.1 and HTTP2 on different ports depending on state of the world
> then.
> The goal of the client itself is to work against HTTP1.1 or HTTP2 with
> minimal or no code path differences and the same for async requests (should
> initially work for both 1.1 and 2 and share majority of code).
> The client should also be able to replace HttpSolrClient and plug into the
> other clients the same way.
> I doubt it would make sense to keep ConcurrentUpdateSolrClient eventually
> though.
> I evaluated some clients and while there are a few options, I went with
> Jetty's HttpClient. It's more mature than Apache HttpClient's support (in 5
> beta) and we would have to update to a new API for Apache HttpClient anyway.
> Meanwhile, the Jetty guys have been very supportive of helping Solr with any
> issues and I like having the client and server from the same project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
