Hi everyone,
Some of us met on 9th of June, 2021 for the planned committer meeting. Here
are the highlights from what was discussed during the ~one hour long
meeting:
1. *Reference Guide Updates* - Cassandra has been working for over an year
on a restructuring and revamp of the already awesome So
I *think* what you are seeing is that “analytics”, “str”, and “scripting” don’t
have any external dependencies, so the jar file is in the /dist directory.
/contrib/{something}/ is where the dependencies for a contrib go.
Honestly, that is probably kind of confusing. I could see an argument f
Hey all,
I ran a "./gradlew --info clean assemble" on "main" recently, and was
surprised to notice that only some contribs make it to the assembled
Solr distribution. "main" has 10 contribs but only 7 of these are
visible in the "contrib/" directory of a Solr distribution.
("analytics, "ltr", and
Hi Lauren,
Firstly, you sent this to Solr's security list, which is for reporting
vulnerabilities or otherwise discussing sensitive topics. I suspect this
was accidental on part and maybe you meant dev@solr.apache.org ? I'm
directing my response to be the dev list instead.
I super quickly skimm
Anyway, returning the original sender:
I had not notice dist updates *are* using the http2 concurrent update
client now.
So that makes a lot of sense on why http 1.1 force improves things. It’s
not nearly as sensitive to connection management.
So I I’d still recommend sticking to http1, but one
FYI https://issues.apache.org/jira/browse/SOLR-15223 will deprecate Apache
HttpClient based SolrClients but I would hope that the Jetty HTTP Client
based SolrClients can be configured to use HTTP 1.1 if desired, although I
have not checked.
~ David Smiley
Apache Lucene/Solr Search Developer
http:/
On Wed, Jun 9, 2021 at 12:25 AM Mark Miller wrote:
>
> Instead of respecting stream contracts, JavaBin is given how much to read
> and it diligently works to read to that point or in some cases it’s own end
> marker.
>
>
That sounds actionable, should it be reading the available contents into an
Though I should say: while I won’t file some large general jira issue about
all the problems that can more visibly manifest in connection fails and
stalls when moving from the Apache client to the jetty client, from the old
SolrClient impl to the Http2 impl, from Http1.1 protocol to 2, how JavaBin
There is no line of code to point to.
I see in the stack trace now that SolrCmdDistributor was updated to the
http2 client.
Lots more stalls and exceptions seen unless that client is changed to use
http1 instead of 2.
But still a lesser problem remains with 1.1.
That is a bit of info on why thi
