then dig...
Mike
On Thu, Jan 13, 2011 at 10:52 AM, Stéphane Delprat
stephane.delp...@blogspirit.com wrote:
I understand less and less what is happening to my solr.
I did a checkIndex (without -fix) and there was an error...
So a did another checkIndex with -fix and then the error was gone
the
same term hits the below exception).
Is there any way I could get a copy of one of your corrupt cases? I
can then dig...
Mike
On Thu, Jan 13, 2011 at 10:52 AM, Stéphane Delprat
stephane.delp...@blogspirit.com wrote:
I understand less and less what is happening to my solr.
I did a checkIndex
during indexing?
Mike
On Wed, Jan 12, 2011 at 10:33 AM, Stéphane Delprat
stephane.delp...@blogspirit.com wrote:
I got another corruption.
It sure looks like it's the same type of error. (on a different field)
It's also not linked to a merge, since the segment size did not change.
*** good
that could cause this.
Mike
On Mon, Jan 10, 2011 at 5:52 AM, Stéphane Delprat
stephane.delp...@blogspirit.com wrote:
Hi,
We are using :
Solr Specification Version: 1.4.1
Solr Implementation Version: 1.4.1 955763M - mark - 2010-06-17 18:06:42
Lucene Specification Version: 2.9.3
Lucene
Hi,
I'm using Solr 1.4.1 (Lucene 2.9.3)
And some segments get corrupted:
4 of 11: name=_p40 docCount=470035
compound=false
hasProx=true
numFiles=9
size (MB)=1,946.747
diagnostics = {optimize=true, mergeFactor=6,
os.version=2.6.26-2-amd64, os=Linux, mergeDocStores=true,
, Jason Rutherglen a écrit :
Stéphane,
I've only seen production index corruption when during merge the
process ran out of disk space, or there is an underlying hardware
related issue.
On Tue, Jan 11, 2011 at 5:06 AM, Stéphane Delprat
stephane.delp...@blogspirit.com wrote:
Hi,
I'm using Solr
Hi,
We are using :
Solr Specification Version: 1.4.1
Solr Implementation Version: 1.4.1 955763M - mark - 2010-06-17 18:06:42
Lucene Specification Version: 2.9.3
Lucene Implementation Version: 2.9.3 951790 - 2010-06-06 01:30:55
# java -version
java version 1.6.0_20
Java(TM) SE Runtime
