dexWriter.java:1638)
>> > at
>> org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1602)
>> > at
>> org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1578)
>> > at
>> > org.apache.solr.update.SolrIndexWriter.close(SolrIndexWriter.j
pulled onto another piece of work.
> >
> > Here is a sample 'fdx size mismatch' exception using the patch Mike
> > supplied:
> >
> > SEVERE: java.lang.RuntimeException: after flush: fdx size mismatch: 1
> docs
> > vs 0 length in
nother piece of work.
>
> Here is a sample 'fdx size mismatch' exception using the patch Mike
> supplied:
>
> SEVERE: java.lang.RuntimeException: after flush: fdx size mismatch: 1 docs
> vs 0 length in bytes of _1i.fdx exists=false didInit=false inc=0 dSO=1
> fieldsW
)
-- Forwarded message --
From: James X
Date: Thu, May 28, 2009 at 7:53 PM
Subject: Fwd: java.lang.RuntimeException: after flush: fdx size mismatch
To: solr-user@lucene.apache.org
My apologies for the delay in running this patched Lucene build - I was
temporarily pulled onto another piece of work
My apologies for the delay in running this patched Lucene build - I was
temporarily pulled onto another piece of work.
Here is a sample 'fdx size mismatch' exception using the patch Mike
supplied:
SEVERE: java.lang.RuntimeException: after flush: fdx size mismatch: 1 docs
vs 0 length i
t;> When you hit this exception, is it always "1 docs vs 0 length in bytes"?
> >>
> >> Mike
> >>
> >> On Wed, May 20, 2009 at 3:19 AM, James X
> >> wrote:
> >> > Hello all,I'm running Solr 1.3 in a multi-core environment. There are
> u
s.
>>
>> Which exact JRE version are you using?
>>
>> When you hit this exception, is it always "1 docs vs 0 length in bytes"?
>>
>> Mike
>>
>> On Wed, May 20, 2009 at 3:19 AM, James X
>> wrote:
>> > Hello all,I'm runn
, 2009 at 3:19 AM, James X
>> wrote:
>> > Hello all,I'm running Solr 1.3 in a multi-core environment. There are up
>> to
>> > 2000 active cores in each Solr webapp instance at any given time.
>> >
>> > I've noticed occasional errors su
On Wed, May 20, 2009 at 11:18 AM, James X
wrote:
> Hi Mike, thanks for the quick response:
>
> $ java -version
> java version "1.6.0_11"
> Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 11.0-b16, mixed mode)
>
> I hadn't noticed the 268m trigger for
ng Solr 1.3 in a multi-core environment. There are up
> to
> > 2000 active cores in each Solr webapp instance at any given time.
> >
> > I've noticed occasional errors such as:
> > SEVERE: java.lang.RuntimeException: after flush: fdx size mismatch: 1
&
Wed, May 20, 2009 at 3:19 AM, James X
wrote:
> Hello all,I'm running Solr 1.3 in a multi-core environment. There are up to
> 2000 active cores in each Solr webapp instance at any given time.
>
> I've noticed occasional errors such as:
> SEVERE: java.lang.RuntimeException
Hello all,I'm running Solr 1.3 in a multi-core environment. There are up to
2000 active cores in each Solr webapp instance at any given time.
I've noticed occasional errors such as:
SEVERE: java.lang.RuntimeException: after flush: fdx size mismatch: 1 docs
vs 0 length in bytes
12 matches
Mail list logo
