On 21/03/16 14:43, Erick Erickson wrote:
Hmmm, you say "where I have many shards and
can't have one problem causing no deletion of old data.".
You then have a shard that, when it comes back up still
has all the old data and that _is_ acceptable? Seems like
that would be jarring to the users when some portion of the
docs in their collection reappeared...
But no, there's no similar option for update that I know of.
Solr tries very hard for consistency and this would lead
to an inconsistent data state.
What is the root cause of your shard going down? That's
the fundamental problem here...
As Erick said, what would be the cause to have a full shard and all its
replicas going down at the same time ?
Usually, if a shard has multiple replicas, and one node goes down, the
replicas on the other nodes should take the lead for this shard, and the
delete queries should work.
--
Renaud Delbru
Best,
Erick
On Mon, Mar 21, 2016 at 7:08 AM, Tali Finelt <tal...@il.ibm.com> wrote:
Hi,
I am using Solr 4.10.2.
When one of the shards in my environment is down and fails to recover -
The process of deleting documents from other shards fails as well.
For example,
When running:
https://<xxx01>:8983/solr/<Collection_name>/update?stream.body=
<delete><query>*:*</query></delete>&commit=true
I get the following error message:
<str name="msg">No registered leader was found after waiting for 4000ms ,
collection: <Collection_name> slice: <xxx02> </str>
This causes a problem in a big environment where I have many shards and
can't have one problem causing no deletion of old data.
Is there a way around that?
To Query on data in such cases, I use shards.tolerant=true parameter to
get results even if some shards are down.
Is there something similar for this case?
Thanks,
Tali
