Oh, also, I don't think not using CFS would lead to this, unless it's
somehow triggering too many file descriptors...
Mike
Cam Bazz wrote:
no. only after that there was a gc error.
I am also not using the compound index file format in order to
increase
indexing speed. could it be becaus
Hmm, you should have seen an exception before that one from optimize.
Can you post the GC error? Was it an OutOfMemoryError situation?
Mike
On Jan 24, 2008, at 5:32 PM, Cam Bazz wrote:
no. only after that there was a gc error.
I am also not using the compound index file format in order to
no. only after that there was a gc error.
I am also not using the compound index file format in order to increase
indexing speed. could it be because of that?
I will run the test case again tomorrow. What can I do to increase logging?
Best,
-C.B.
On Jan 24, 2008 11:52 PM, Michael McCandless <[EMA
That means that one of the merges, which run in the background by
default with 2.3, hit an unhandled exception.
Did you see another exception logged / printed to stderr before this
one?
Mike
Cam Bazz wrote:
Does anyone have any idea about the error I got while indexing?
Best Regards,
Does anyone have any idea about the error I got while indexing?
Best Regards,
-C.B.
Exception in thread "main" java.io.IOException: background merge hit
exception: _kq:C962870 _kr:C2591 into _ks [optimize]
at org.apache.lucene.index.IndexWriter.optimize(IndexWriter.java:1749)
at org.apach
HI
Thanks for the update
This does not occur often. Happens occassionally. I'll further monitor and
let you know if I find some thing
If it happens will do the verbose output for IndexWriter.setInfoStream
Regards
Bharath
On 6/12/07, Michael McCandless <[EMAIL PROTECTED]> wrote:
This looks
This looks like a rather serious error. It seems like that file has
somehow gone missing in your index.
On adding a given document, Lucene has flushed its buffered documents
and is attempting to merge segments together when it finds that one of
the segments that it thinks exists (_v3.cfs) and ne
Hi
We run a batch job written on Java that reads a Oracle DB and creates a
Lucene INDEX. We use Compass interface to do the index creation operations
This is a scheduled job and this is a batch insert transaction job
suddenly we are getting the following exception.
I wnet through the forum and var
TECTED]>
Para: java-user@lucene.apache.org
Enviadas: Sábado, 26 de Maio de 2007 9:31:39
Assunto: Re: exception while indexing
This looks like one of the issues that was fixed in 2.1. Is it possible to
test 2.1
to see if it still happens?
Mike
"Mohammad Norouzi" <[EMAIL PROTECT
This looks like one of the issues that was fixed in 2.1. Is it possible to
test 2.1
to see if it still happens?
Mike
"Mohammad Norouzi" <[EMAIL PROTECTED]> wrote:
> Hi
> I am using Lucene 2.0.0
> I get following exception while indexing...
> is there anyone has fa
Hi
I am using Lucene 2.0.0
I get following exception while indexing...
is there anyone has faced this exception?
thanks
java.io.IOException: Cannot rename E:\index-lab\segments.new to
E:\index-lab\segments
at org.apache.lucene.store.FSDirectory.renameFile(FSDirectory.java
:294
11 matches
Mail list logo
