Hi,
I usually install solr by manually downloading tarballs from mirrors. I
don't always want to install the latest version when provisioning a
new server. I upgrade after a manual overview of the new release.
However, I've tested a couple of mirrors [0] and the main distribution
point [1]: of
Hi,
Several older versions of Solr are available as Docker images:
https://hub.docker.com/_/solr/
If using Docker is not an option, you can still extract the Solr
distribution from those images by starting a container and copying the
relevant path recursively to the host system.
Cheers.
On Wed,
Hello Team
I have Solr cloud 5.4.1 set up having a collection with 4 shards &
replication factor of 2
If i run a solr query with facet on a field & fact.limit as 1000 and rows=0
how many java objects corresponding to facet gets created in each shard for
following scenario
1) If total no of unique
Hello,
All ASF project releases are permanently available at the archive:
http://archive.apache.org/dist/lucene/solr/
Future versions of Solr are probably here:
http://archive.apache.org/dist/solr/
Regards,
Markus
Op wo 10 mrt. 2021 om 11:41 schreef Christian Ortner :
> Hi,
>
> Several older v
If I understand correctly, this ticket is about registering a new, custom
expression. SolrClientCache and CloudSolrStream are more like backbone classes
working behind every streaming expression. Is it really possible to modify them
this way?
Sent from Mail for Windows 10
From: Joel Bernstein
> even if we could load the elevate.xml file from the data
folder in Cloud (or changing it directly in zk), does this make sense in
terms of performance? We have frequent commits and a big elevate.xml file.
In terms of performance a big elevate.xml should not be an issue. The
structure used for qu
Hi,
A client has a SolrCloud 8.4 setup with two nodes, and one collection with one
shard and replicationFactor=2.
Of course we want search traffic to be evenly distributed between the two
replicas.
The client is using plain HTTP requests, no SolrJ or anything fancy, and sends
all requests to on
I believe a server will always try to prefer local cores. Can you do an
experiment with 3 nodes, and send http queries to the node not hosting any
replicas? That should confirm the balanced distribution.
If you have multiple shards, the receiving server will forward the requests
for shards it does
I could be wrong, but i dont think preferLocalShards is the default in
multi-shard use cases.
On Wed, Mar 10, 2021 at 9:07 AM Mike Drob wrote:
> I believe a server will always try to prefer local cores. Can you do an
> experiment with 3 nodes, and send http queries to the node not hosting any
>
Yes, i enable LTR and reload the core..
On Wed, Mar 10, 2021, 02:33 Diego Ceccarelli
wrote:
> also you might need to reload the core to see the features / models loaded:
>
> https://solr.apache.org/guide/8_5/coreadmin-api.html see RELOAD
>
> On Wed, Mar 10, 2021, 06:33 Jörn Franke wrote:
>
> >
You say not "anything fancy" -- depending on how you define "fancy", if you
have an explicit `shards.preference` param, based on the version you're
running (8.4) you might also take a look at
https://issues.apache.org/jira/browse/SOLR-14471. (If SOLR-14471 is the
problem, removing the explicit `sha
We have not set any shard.preference, and I also think preferLocal defaults to
false, i.e random
Earlier we had 2 shares for the same collection (both existed on both nodes)
and then requests were distributed to both nodes. That’s why, when we went to 1
shard, I was wondering if the “single-sha
Ah, I missed "single shard" ... this looks relevant:
https://issues.apache.org/jira/browse/SOLR-12217
On Wed, Mar 10, 2021 at 12:43 PM Jan Høydahl wrote:
> We have not set any shard.preference, and I also think preferLocal
> defaults to false, i.e random
>
> Earlier we had 2 shares for the same
The shortCircuit parameter might explain it?
https://github.com/apache/solr/blob/releases/lucene-solr%2F8.4.0/solr/core/src/java/org/apache/solr/handler/component/HttpShardHandler.java#L401
Christine
From: users@solr.apache.org At: 03/10/21 17:42:46To: users@solr.apache.org
Subject: Re: Solr no
all of the "routing" logic (preferLocal, shards.preference, etc...) really
only comes into play once solr "code" (either CloudSolrClient, or a solr
server recieving a request) decides that it needs to make a remote
connection.
If a node recieves a request, and it has a local core capable of ha
: Ah, I missed "single shard" ... this looks relevant:
: https://issues.apache.org/jira/browse/SOLR-12217
That improvement still isn't going to impact Jan's situation where the
*client* isn't SolrJ ... as the description says:
>> NOTE: This Jira doesn't cover the single-sharded collections case
Aha, I'm starting to see what is happening here.
So on the server side, a node hosting one of N replicas for a shard, and that
collection is single-sharded, then no randomization or forwarding will ever
take place.
Before SOLR-12217 it would not happen when using SolrJ either, but after
SOLR-12
: Is there any way whatsoever to solve this on the Solr side only?
:
: Only I can think of is to send all requests to a 3rd node in the cluster
: that does not have a core for the collection, then it will balance
: between the two :)
correct -- you can create a Solr node w/o any cores that wil
> no -- this won't work, because the requerst your remote client sends will
> need to specify the actual collection you want to query, and when the node
I was more thinking of some explicit &collections=otherColl or
&shards=other_1,other_2 but easier to just send to a node without that
collect
Hi everyone,
Does anyone know if CVE-2020-27223 [1] impacts Solr? This is a
vulnerability in jetty-http-9.4.27.v20200227.jar which we ship with Solr
8.6.1.
Thanks,
Steven
[1] https://nvd.nist.gov/vuln/detail/CVE-2020-27223
Thanks I'll check that out. :)
Shaun
On Tue, 9 Mar 2021 at 22:31, Jörn Franke wrote:
> From the Solr ref guide: you forgot the flatten graph filter at the end -
> this is needed for any graph filter you use : class="solr.FlattenGraphFilterFactory"/>
>
> > Am 09.03.2021 um 22:21 schrieb Shaun
To expand on Markus's comment...
1) The availability for downloading "Past Versions" of Solr is spelled out
on the downloads page:
https://solr.apache.org/downloads.html#past-versions
2) The mirror network, by design, is only suppose to host "current,
recommended releases" -- the specific d
: > that seems... dangerous. you could easily wind up in a situation where
: > nodes just keep trying to forward forever?
:
: There is some special http parameter being added when forwarding
: requests, so I'm sure each node will be able to decide whether it should
: act as LB or if it is sup
>> 2) a single "extra" solr node in the cluster can be used as a "self
configuring" load balancer
I’ve thought about this a bunch before, are there mechanisms to instruct
Solr to not host shards for this purpose? Maybe it deserves its own
discussion.
On Wed, Mar 10, 2021 at 5:14 PM Chris Hostette
You could even run a separate Solr on the node just to redistribute the queries.
But if I was going to do that, I’d run a copy of nginx as a load balancer
instead.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Mar 10, 2021, at 4:51 PM, Mike Drob w
I have a simple Solr query component that does some exact match processing
by replacing qf and pf params in incoming search requests with new values
that point to the fields that do not do stemming, synonymization etc.
This works as expected. However in a distributed context (not using
SolrCloud,
Hi Ere
Thanks for the help on this. I have raised SOLR-15246 to cover this.
Many thanks
Matthew
Matthew Flowerday | Consultant | ULEAF
Unisys | 01908 774830| matthew.flower...@unisys.com
Address Enigma | Wavendon Business Park | Wavendon | Milton Keynes | MK17
8LX
THIS COMMUNICATION MAY CON
27 matches
Mail list logo
