n).
> >> This pre-production is used to check data before dumping in Production.
> >>
> >>
> >> Cordialement, Best Regards
> >> Bruno Mannina
> >> www.matheo-software.com
> >> www.patent-pulse.com
> >> Mob. +33 0 634 421 817
> &
d'origine-
De : Robi Petersen [mailto:robip...@gmail.com]
Envoyé : lundi 7 avril 2025 02:12
À : users@solr.apache.org
Objet : Re: Solr error...
Hi Bruno,
As an aside, in general you'd want your staging (pre-prod) solr instance to
exactly match your production solr instance in every way (l
theo-software.com
> www.patent-pulse.com
> Mob. +33 0 634 421 817
>
>
> -Message d'origine-----
> De : Robi Petersen [mailto:robip...@gmail.com]
> Envoyé : lundi 7 avril 2025 02:12
> À : users@solr.apache.org
> Objet : Re: Solr error...
>
> Hi Bruno,
uction solr (I used a Solr 8.11.3 on my production).
>> This pre-production is used to check data before dumping in Production.
>>
>>
>> Cordialement, Best Regards
>> Bruno Mannina
>> www.matheo-software.com
>> www.patent-pulse.com
>> Mob. +33 0 634 421 817
>>
uction.
>
>
> Cordialement, Best Regards
> Bruno Mannina
> www.matheo-software.com
> www.patent-pulse.com
> Mob. +33 0 634 421 817
>
>
> -Message d'origine-
> De : Colvin Cowie [mailto:colvin.cowie@gmail.com]
> Envoyé : vendredi 4 avril 2025 11:57
>
---
De : Colvin Cowie [mailto:colvin.cowie@gmail.com]
Envoyé : vendredi 4 avril 2025 11:57
À : users@solr.apache.org
Objet : Re: Solr error...
Hello,
I think we might need some more context here, that is to say, why are you using
Solr 5.5.1? That was released in 2016 and is very much
Hello,
I think we might need some more context here, that is to say, why are you
using Solr 5.5.1? That was released in 2016 and is very much out of date
and unsupported (and will contain a number of critical CVEs).
So rather than trying to make it work, can you instead move to the latest
release
I have also gotten myself into situations where the leader election
looked broken and finding + restarting the overseer has always been
the best method to fix it. You can find this stuff by browsing
zookeeper.
On Mon, Jun 5, 2023 at 9:13 AM Walter Underwood wrote:
>
> I’ve seen this kind of thi
I’ve seen this kind of thing happen when the overseer is stuck for some reason.
Look for a long queue of work for the overseer in zookeeper. I’ve fixed that by
restarting the node which is the overseer. The new one wakes up and clears the
queue. I’ve only seen that twice.
Wunder
> On Jun 5, 20
Hi,
One possible reason for this could be that a shard leader experienced a high
load (or crash), causing its Zookeeper client timeout, e.g. losing its
live_nodes entry.
That would cause a leader election, and a replica would become the new leader.
Once the original leader re-joins it will no lon
10 matches
Mail list logo
