; After this, the cluster state seems to be fine, and I'm not being spammed
> with errors in the log files.
>
> Bottom line is that the issues are fixed for now it seems, but I still find
> it weird that Solr was not able to fully receover.
>
> // Henrik Ossipoff
>
> -
27;m not being spammed
> with errors in the log files.
>
> Bottom line is that the issues are fixed for now it seems, but I still find
> it weird that Solr was not able to fully receover.
>
> // Henrik Ossipoff
>
> -Original Message-
> From: Mark Miller [mailto:
_suggest_shard1_replica2
>
> After this, the cluster state seems to be fine, and I'm not being spammed
> with errors in the log files.
>
> Bottom line is that the issues are fixed for now it seems, but I still find
> it weird that Solr was not able to fully receover.
>
> // Henr
ble to fully receover.
// Henrik Ossipoff
-Original Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: 10. november 2013 19:27
To: solr-user@lucene.apache.org
Subject: Re: SolrCloud never fully recovers after slow disks
Which version of solr are you using? Regardless of your env,
: Re: SolrCloud never fully recovers after slow disks
Which version of solr are you using? Regardless of your env, this is a fail
safe that you should not hit.
- Mark
> On Nov 5, 2013, at 8:33 AM, Henrik Ossipoff Hansen
> wrote:
>
> I previously made a post on this, but have since
Which version of solr are you using? Regardless of your env, this is a fail
safe that you should not hit.
- Mark
> On Nov 5, 2013, at 8:33 AM, Henrik Ossipoff Hansen
> wrote:
>
> I previously made a post on this, but have since narrowed down the issue and
> am now giving this another try, w
Hey Erick,
I have tried upping the timeouts quite a bit now, and have tried upping the
zkTimeout setting in Solr itself (I found a few old posts on the mailing list
suggesting this).
I realise this is a sort of weird situation, where we are actually trying to
work around some horrible hardware
Right, can you up your ZK timeouts significantly? It sounds like
your ZK timeout is short enough that when your system slows
down, the timeout is exceeded and it's throwing Solr
into a tailspin
See zoo.cfg.
Best,
Erick
On Tue, Nov 5, 2013 at 3:33 AM, Henrik Ossipoff Hansen <
h...@entertainm
I previously made a post on this, but have since narrowed down the issue and am
now giving this another try, with another spin to it.
We are running a 4 node setup (over Tomcat7) with a 3-ensemble external
ZooKeeper. This is running no a total of 7 (4+3) different VMs, and each VM is
using our
