lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-12297) Create a good SolrClient for SolrCloud paving the way for async requests, HTTP2, multiplexing, and the latest & greatest Jetty features.
Date Tue, 15 May 2018 04:55:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475280#comment-16475280
] 

Mark Miller commented on SOLR-12297:
------------------------------------

This is going to be a bit of a slow burn, I just kind of hack on it here and there when I
have the time, but just to start measuring some progress:

Currently approx 40-50 of the 806 core tests don't pass with everything forced to full Http2
and usage of the new Http2SolrClient.

I've got the new V2 API stuff working it seems.
 Proxying to remote replicas is basically working.

However, minimally still to do:

TODO: Finish client side SSL support
 TODO: All tests passing
 TODO: Tune settings / streaming payloads vs not, etc
 TODO: Configure shipping Jetty
 TODO: Serve HTTP2 and HTTP on same port
 TODO: Multiple content streams with Http2SolrClient
 TODO: Finish and finalize APIs, especially Async API
TODO: Performance and scale testing

I havn't focused on just extracting the client for http 1.1 use yet because I'm learning more
and more about what needs to happen with it as I work through many of the outstanding issues.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message