Hi
Since merging is done in separate threads, I am actually firing multiple
merges concurrently. That may be causing the problem. Is it possible to make
merges a synchronous operation?
Sumanta
-Original Message-
From: Sumanta Bhowmik [mailto:sumanta.bhow...@guavus.com]
Sent: Friday
there is a way to know the status of the merge operation?
Sumanta
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Thursday, August 27, 2009 2:30 PM
To: Sumanta Bhowmik
Cc: java-user@lucene.apache.org
Subject: Re: Merge Exception in Lucene 2.4
Was this a
cc version 4.1.2 20071124
(Red Hat 4.1.2-42)
This exception occurs after we have indexed more than 100 gb of data. I will
try running with -Xint to see if I can avoid this exception.
Regards
Sumanta
-Original Message-----
From: Sumanta Bhowmik [mailto:sumanta.bhow...@guavus.com]
Sent: Monday,
@lucene.apache.org
Subject: Re: Merge Exception in Lucene 2.4
That code looks fine...
What OS/filesystem are you using?
Can you make a small test case that shows the issue?
Mike
On Thu, Aug 20, 2009 at 7:41 AM, Sumanta
Bhowmik wrote:
> We put all the IndexWriters in an array which is defined by
>
&
u merge 6 IndexWriters?
Mike
On Thu, Aug 20, 2009 at 5:21 AM, Sumanta
Bhowmik wrote:
> I checked at http://issues.apache.org/jira/browse/LUCENE-1282
> SegmentMerger.java has this code
>
> TermFreqVector[] vectors = reader.getTermFreqVectors(docNum);
> termVectorsWriter.addAllDocVec
t fixed in jdk6u10 and above
(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6707044) ?
Regards
Sumanta
-Original Message-----
From: Sumanta Bhowmik [mailto:sumanta.bhow...@guavus.com]
Sent: Thursday, August 20, 2009 1:15 PM
To: java-user@lucene.apache.org
Subject: Merge Exception in
Hi
I am getting this issue in Lucene2.4 when I try to merge multiple
IndexWriters(generally 6)
sh-3.2# Exception in thread "Lucene Merge Thread #5"
org.apache.lucene.index.MergePolicy$MergeException: java.io.IOException:
read past EOF
at
org.apache.lucene.index.ConcurrentMergeSche
Hi
I found that a query "NOT num_pkts:1024 OR src_port:80" behaves the same as
"NOT num_pkts:1024 AND src_port:80". The actual query is
(start_utc:[1230748200 TO 1230768000] OR end_utc:[1230748200 TO 1230768000])
AND (num_pkts:1024 OR NOT num_bytes:40960) but it behaves as if it is
(
