Ahhh, ok. When you reloaded the cores, did you do it core-by-core?
Yes, but maybe we reloaded the wrong core or something like that. We
also noticed that the startTime doesn't update in the admin-ui while
switching between cores (you have to reload the page). We still use
4.8.1, so maybe it
Hi,
this _sounds_ like you somehow don't have indexed=true set for the
field in question.
We investigated a lot more. The CheckIndex tool didn't find any error.
We now think the following happened:
- We changed the schema two months ago: we changed a field to
indexed=true. We reloaded the
Ahhh, ok. When you reloaded the cores, did you do it core-by-core?
I can see how something could get dropped in that case.
However, if you used the Collections API and two cores mysteriously
failed to reload that would be a bug. Assuming the replicas in question
were up and running at the time
bq: You say in our case some docs didn't made it to the node, but
that's not really true: the docs can be found on the corrupted nodes
when I search on ID. The docs are also complete. The problem is that
the docs do not appear when I filter on certain fields
this _sounds_ like you somehow don't
Hi Erick,
Thank you for your detailed reply.
You say in our case some docs didn't made it to the node, but that's
not really true: the docs can be found on the corrupted nodes when I
search on ID. The docs are also complete. The problem is that the docs
do not appear when I filter on certain
Subject: Re: Solrcloud Index corruption
Hi Erick,
Thank you for your detailed reply.
You say in our case some docs didn't made it to the node, but that's not really
true: the docs can be found on the corrupted nodes when I search on ID. The
docs are also complete. The problem is that the docs do
to the leader of the
appropriate shard, no matter what server first receives the request.
-Original Message-
From: Martin de Vries [mailto:mar...@downnotifier.com]
Sent: Thursday, March 05, 2015 4:14 PM
To: solr-user@lucene.apache.org
Subject: Re: Solrcloud Index corruption
Hi Erick
On 3/5/2015 3:13 PM, Martin de Vries wrote:
I understand there is not a master in SolrCloud. In our case we use
haproxy as a load balancer for every request. So when indexing every
document will be sent to a different solr server, immediately after
each other. Maybe SolrCloud is not able to
Wait up. There's no master index in SolrCloud. Raw documents are
forwarded to each replica, indexed and put in the local tlog. If a
replica falls too far out of synch (say you take it offline), then the
entire index _can_ be replicated from the leader and, if the leader's
index was incomplete then
Hi,
We have index corruption on some cores on our Solrcloud running version
4.8.1. The index is corrupt on several servers. (for example: when we do
an fq search we get results on some servers, on other servers we don't,
while the stored document contains the field on all servers).
A full
We had a similar issue, when this happened we did a fetch index on each core
out of sync to put them back right again
Sent from my iPhone
On 5 Mar 2015, at 14:40, Martin de Vries mar...@downnotifier.com wrote:
Hi,
We have index corruption on some cores on our Solrcloud running version
Subject: Re: Solrcloud Index corruption
We had a similar issue, when this happened we did a fetch index on each core
out of sync to put them back right again
Sent from my iPhone
On 5 Mar 2015, at 14:40, Martin de Vries mar...@downnotifier.com wrote:
Hi,
We have index corruption on some
Hi Andrew,
Even our master index is corrupt, so I'm afraid this won't help in our
case.
Martin
Andrew Butkus schreef op 05.03.2015 16:45:
Force a fetchindex on slave from master command:
http://slave_host:port/solr/replication?command=fetchindex - from
13 matches
Mail list logo
