Hi Rodolfo
Random ≠ unique. If you really need a tie breaker, you'll have to sort on
the uiqueKey field.
What is your use case here? When using a cursor, sorting on a random field
will yield confusing results.
Thomas
Op ma 30 aug. 2021 om 17:33 schreef rgamarra :
> Hi there! I'm using random f
Hi All,
We have recently upgraded solr cloud from 8.1 to 8.8.1. After upgrade we
are facing duplicate values in solr data.
Please find the below screenshot for your reference.
Could someone please suggest ways to avoid the issue.
[image: image.png]
--
Thanks and Regards,
Hari
Mobile:97907565
Hi Solr Experts,
I am using Solr cloud 8.9.0 . For quite some time I have observed that core
reload activity stops the index replication .
2021-04-23 18:34:31.093 ERROR (indexFetcher-12109-thread-1) [ ]
o.a.s.h.IndexFetcher User aborted Replication
2021-04-23 18:34:31.103 INFO (pool-5-thread-
Hi there! I'm using random fields (eg sort=random_1234 DESC) as a tie
breaker.
I'm wondering the underlying random sequence how many digits uses for each
generated number.
My result sets my contain (in principle) millions of results, so I would
like to have an estimation of possible clashes (ie t
Dear Solr user community,
I have started to use the Solr 8.9 suggester. The definition is as follows:
{
"searchComponent":{
"suggest_test":{
"name":"suggest_test",
"class":"solr.SuggestComponent",
"suggester":{
"name":"combinedSuggester",
In logs I could see this WARN.
2021-08-30 13:15:52.301 WARN (zkCallback-12-thread-3) [c:quoteStore
s:shard1 r:core_node6 x:quoteStore_shard1_replica_n5]
o.a.s.c.RecoveryStrategy Stopping recovery for
core=[quoteStore_shard1_replica_n5] coreNodeName=[core_node6]
On Mon, Aug 30, 2021 at 6:43 PM Ha
Hi Zisis,
Thanks for your email.
We are suspecting the issue with one particular solr collection(or store).
Wherever the replicas of that store are present that nodes are going down.
Also now that shard is in recovery mode and Leader is not elected. Could
you please suggest something to bring up
My guess is that the Solr/Zookeeper communication issues are due to GC pauses.
You are saying that you end up with OOM problems. High memory usage puts
pressure on GC. Long GC pauses lead to timeouts in Solr/Zookeeper
communication. We've seen that happening.
First thing I'd do is to get a hea
I can’t help beyond such, I don’t like solr cloud nor zookeeper, I will always,
if I can help it, stick to standalone solr instance.
> On Aug 30, 2021, at 3:23 AM, HariBabu kuruva
> wrote:
>
> Hi Dave
>
> We tried setting the memory as per your suggestions.
>
> But still I see that the sol
Hi Dave
We tried setting the memory as per your suggestions.
But still I see that the solr is going down in a couple of minutes with an
OOM error. Also in the solr logs it says below connectivity issue between
solr and zookeeper. Please advise.
Zookeeper is running fine.
2021-08-30 06:24:13.0
10 matches
Mail list logo
