Shard relocating and I don't know why

Hi, I have a 5 nodes cluster (solr-7.4.0 + zookeeper-3.4.12) with relatively small collection count. Each core has 2 shards, 1 replica (totalling 4 items). >From time to time, without notice, I see that shards get relocated but sometimes this happens [1]: shard (shard2 in this example) seems to go

enableRemoteStreaming+enableStreamBody-change in Solr 8.11.3

The bin/solr script in the binary release of Solr 8.11.3 does not include the lines to handle the environment variables SOLR_ENABLE_{REMOTE_STREAMING,STREAM_BODY} introduced in place of the solrconfig.xml attributes enable{RemoteStreaming,StreamBody} removed in SOLR-14853. Was that on purpose and

Re: enableRemoteStreaming+enableStreamBody-change in Solr 8.11.3

Hi, You are right that the env.vars approach was not backported to 8.x. The workaround you can use in solr.in.sh is: The workaround is to set in solr.in.sh: SOLR_OPTS="$SOLR_OPTS -Dsolr.enableRemoteStreaming=true -Dsolr.enableStreamBody=true" This should have been documented in the reference

Re: enableRemoteStreaming+enableStreamBody-change in Solr 8.11.3

Jan writes: > You are right that the env.vars approach was not backported to 8.x. Thanks for the confirmation that it wasn't just me. > I'll reply to the dev thread as well with a followup for > documentation. Perfect - thanks a lot! Best regards, Adam -- "Frank, don't be paranoid."

CVE-2024-31391: Apache Solr Operator: Solr-Operator liveness and readiness probes may leak basic auth credentials

Severity: moderate Affected versions: - Apache Solr Operator 0.3.0 through 0.8.0 Description: Insertion of Sensitive Information into Log File vulnerability in the Apache Solr Operator. This issue affects all versions of the Apache Solr Operator from 0.3.0 through 0.8.0. When asked to boots

[Operator] [ANNOUNCE] Apache Solr Operator v0.8.1 released

The Apache Solr PMC is pleased to announce the release of the Apache Solr Operator v0.8.1. The Apache Solr Operator is a safe and easy way of managing a Solr ecosystem in Kubernetes. This release contains several bug fixes, some of which are highlighted below. It also resolves CVE-2024-31391, a c

Unique key not being generated by UUIDUpdateProcessorFactory

I'm currently updating a Solr instance from 5.5 to 9.4 (and to solr cloud). More precisely, I'm starting with base config files from 9.4 and updating it to be equivalent to one used for 5.5 However, I have run into an issue with the unique key, and I cannot see what the issue is. We expect the id

Re: Problem with word separators?

Most query parsers don't support wildcards in phrases. Do you really need phrase matches in your article numbers? If so you might need to experiment with the ComplexPhraseQueryParser . Your example

Re: [EXTERNAL] Unique key not being generated by UUIDUpdateProcessorFactory

You have uuid in the solrconfig.xml but id in the managed-schema. On 4/12/24, 11:50 AM, "David Driver" mailto:david.dri...@enactor.co.uk>> wrote: I'm currently updating a Solr instance from 5.5 to 9.4 (and to solr cloud). More precisely, I'm starting with base config files from 9.4 and updat