there progress regarding this?
Some kind of configuration that can mitigate this?
Maybe this is a lucene issue.
Thanks,
Bill OConnor (www.plos.org)
;
>>> for host in $hosts
>>> do
>>> host="${host}.cloud.cheggnet.com"
>>> echo restarting Solr on $host
>>> ssh $host 'cd /apps/solr6 ; sudo -u bin bin/solr stop; sudo -u bin
>>> bin/solr start -cloud -h `hostname`&
or 4? I'm guessing 5, but
want to check unlikely possibilities.
Next question: I'm assuming all your nodes have been upgraded to Solr 6, right?
Best,
Erick
On Wed, Sep 20, 2017 at 7:18 PM, Bill Oconnor wrote:
> I have no clue where that number comes from it does not seem to be in th
: Replicates not recovering after rolling restart
> On Sep 20, 2017, at 6:15 PM, Bill Oconnor wrote:
>
> I restart using the standard "sudo service solr start/stop"
You might look into what that actually does.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
#x27;.cluster.live_nodes[]' | sort`
>
> for host in $hosts
> do
> host="${host}.cloud.cheggnet.com"
> echo restarting Solr on $host
> ssh $host 'cd /apps/solr6 ; sudo -u bin bin/solr stop; sudo -u bin
> bin/solr start -cloud -h `hostname`'
> done
&
Hello,
Background:
We have been successfully using Solr for over 5 years and we recently made the
decision to move into SolrCloud. For the most part that has been easy but we
have repeated problems with our rolling restart were server remain functional
but stay in Recovery until they stop tr
