Thanks for the explanation Erick, that makes sense!
Matt
On 21/09/2018 15:50, Erick Erickson wrote:
The disk corruption is, of course, a red flag and likely the root cause.
As for how it replicated let's assume a 2 replica shard (leader +
follower). If the follower ever went into full recove
The disk corruption is, of course, a red flag and likely the root cause.
As for how it replicated let's assume a 2 replica shard (leader +
follower). If the follower ever went into full recovery it would use
old-style replication to copy down the entire index, corrupted index
and all, from the lea
sorry I forgot to say, the exceptions are not for every document, but only
for a few...
regards,
Victor
Victor Ruiz wrote
> Hi guys,
>
> I'm getting exceptions in a Solr slave, when accessing TermVector
> component and RealTimeGetHandler. The weird thing is, that in the master
> and in one of th
If you need to fix the index and maybe lose some data (in bad segments),
check Lucene's CheckIndex (cmd-line app)
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: Jake Brownell
> To: "solr-user@lucene.apache.org"
> Sent: Thu, January
Yes, that would be helpful to include, sorry, the official 1.4.
-Original Message-
From: Ryan McKinley [mailto:ryan...@gmail.com]
Sent: Thursday, January 07, 2010 2:15 PM
To: solr-user@lucene.apache.org
Subject: Re: Corrupted Index
what version of solr are you running?
On Jan 7, 2010
what version of solr are you running?
On Jan 7, 2010, at 3:08 PM, Jake Brownell wrote:
Hi all,
Our application uses solrj to communicate with our solr servers. We
started a fresh index yesterday after upping the maxFieldLength
setting in solrconfig. Our task indexes content in batches and
