Hello folks,
We’re running our SolrCloud cluster in Kubernetes. Recently we’ve upgraded from
8.11 to 9.0 (and eventually to 9.1).
Fully reindexed collections after upgrade, all looking good, no errors,
response time improvements are noticed.
We have the following specs:
collection size:
22M d
Op za 3 dec. 2022 om 18:47 schreef Shawn Heisey :
> On 12/3/22 10:38, dmitri maziuk wrote:
> > On 2022-12-02 7:41 PM, Shawn Heisey wrote:
> >
> >> I'm curious as to why those entities are displaying as text instead
> >> of being interpreted by the browser as a zero-width space.
> >
> > I am curiou
I'm not sure this is the issue, but maybe its http2 vs http1.
Could you retry with the following set on the cluster?
-Dsolr.http1=true
On Mon, Dec 5, 2022 at 5:08 AM Nick Vladiceanu
wrote:
> Hello folks,
>
> We’re running our SolrCloud cluster in Kubernetes. Recently we’ve upgraded
> from 8.
: today we updated solr to version 9.1 (lucene version 9.3)
Which version did you upgrade from?
: Since then we noticed plenty of TooManyNestedClauses in the logs. Our
: setting for maxClauseCount is 1024
Exactly where/how are you setting that? There are 2 settings related to
this...
https:
: POC would be to add a function in the plugin.. which would query all the
: documents locally (Say 100+ Million Documents) and update 1 or 2 fields
: with a particular value.
:
: As the plugin would be local to this core.. wanted to avoid HTTP calls.
I'm assuming here that you mean you want
Hi Hoss,
I'm happy to provide some details as I still do not really understand the
difference to the situation before.
In case something like categoryId:[1 TO 1] also gets converted to some
boolean term, then it's clear to me.
Otherwise I do not understand why half the boolean clauses (512 + 1)
al
