I brought down the afflicted servers, waited 5 min, then brought them back up
very slowly. That fixed the problem. The bad shard was assigned a leader.
Great advice as usual.
Erick Erickson wrote
> Yes. If indexing went through you'd lose docs so indexing will fail.
> Querying will fail too unless
Yes. If indexing went through you'd lose docs so indexing will fail.
Querying will fail too unless you set shards.tolerant.
You really wouldn't want your docs lost is the reasoning.
On Feb 2, 2017 6:56 AM, "tedsolr" wrote:
> Can I assume that without a leader the shard will not respond to write
Can I assume that without a leader the shard will not respond to write
requests? I can search on the collection. If I can't update docs or add any
new docs then this becomes an emergency.
Erick Erickson wrote
> It's worth a try to take down your entire cluster. Bring one machine
> back up at a ti
It's worth a try to take down your entire cluster. Bring one machine
back up at a time. There _may_ be something like a 3 minute wait
before each of the replicas on that machine come up, the leader
election process has a 180 second delay before the replicas on that
node take over leadership to wait
Sounds similar to a thread last year:
http://lucene.472066.n3.nabble.com/Node-not-recovering-leader-elections-not-occuring-tp4287819p4287866.html
On 2/1/17, 7:49 AM, "tedsolr" wrote:
I have version 5.2.1. Short of an upgrade, are there any remedies?
Erick Erickson wrote
>
I have version 5.2.1. Short of an upgrade, are there any remedies?
Erick Erickson wrote
> What version of Solr? since 5.4 there's been a FORCELEADER colelctions
> API call that might help.
>
> I'd run it with the newly added replicas offline. you only want it to
> have good replicas to choose fr
could be the issue
Regards,
~Sri
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Wednesday, February 01, 2017 10:39 AM
To: solr-user
Subject: Re: Collection will not replicate
What version of Solr? since 5.4 there's been a FORCELEADER colelctions API
What version of Solr? since 5.4 there's been a FORCELEADER colelctions
API call that might help.
I'd run it with the newly added replicas offline. you only want it to
have good replicas to choose from.
Best,
Erick
On Wed, Feb 1, 2017 at 6:48 AM, tedsolr wrote:
> Update! I did find an error:
>
>
Update! I did find an error:
2017-02-01 09:23:22.673 ERROR org.apache.solr.common.SolrException
:org.apache.solr.common.SolrException: Error getting leader from zk for
shard shard1
Caused by: org.apache.solr.common.SolrException: Could not get leader props
at
org.apache.solr.cloud.Zk