On Mon, Nov 30, 2009 at 2:34 PM, Michael McCandless
wrote:
> On Mon, Nov 30, 2009 at 7:22 AM, jm wrote:
>> No other exceptions I could spot.
>
> OK
>
>> OS: win2003 32bits, with NTFS. This is a vm running on vmware fusion on a
>> mac.
>
> That should be fine...
>
>> jvm: I made sure, java versio
On Mon, Nov 30, 2009 at 7:22 AM, jm wrote:
> No other exceptions I could spot.
OK
> OS: win2003 32bits, with NTFS. This is a vm running on vmware fusion on a mac.
That should be fine...
> jvm: I made sure, java version "1.6.0_14"
Good.
> IndexWriter settings:
> writer.setMaxFieldLengt
No other exceptions I could spot.
OS: win2003 32bits, with NTFS. This is a vm running on vmware fusion on a mac.
jvm: I made sure, java version "1.6.0_14"
IndexWriter settings:
writer.setMaxFieldLength(maxFieldLength);
writer.setMergeFactor(10);
writer.setRAMBufferSizeMB(
I'll check all thsese with my ops guy on monday and report back.
Thanks for the interest.
On Fri, Nov 27, 2009 at 4:00 PM, Michael McCandless
wrote:
> Any Lucene-related exceptions hit in your env? What OS (looks like
> Windows, but which one?), filesystem are you on?
>
> And are you really cert
Any Lucene-related exceptions hit in your env? What OS (looks like
Windows, but which one?), filesystem are you on?
And are you really certain about the java version being used in your
production env? Don't just trust which java your interactive shell
finds on its PATH -- double check how your a
On Fri, Nov 27, 2009 at 6:23 AM, jm wrote:
> Ok, I got the index from the production machine, but I am having some
> problem to find the index..., our process deals with multiple indexes,
> in the current exception I cannot see any indication about the index
> having the issue. I opened all my in
I manually did CheckIndex in all indexes and found two with issues:
first
Segments file=segments_42w numSegments=21 version=FORMAT_HAS_PROX [Lucene 2.4]
1 of 21: name=_109 docCount=10410
compound=true
hasProx=true
numFiles=1
size (MB)=55,789
no deletions
test: open reader
Ok, I got the index from the production machine, but I am having some
problem to find the index..., our process deals with multiple indexes,
in the current exception I cannot see any indication about the index
having the issue. I opened all my indexes with luke and old opened
succesfully, some had
Also, if you're able to reproduce this, can you call
writer.setInfoStream and capture & post the resulting output leading
up to the exception?
Mike
On Thu, Nov 26, 2009 at 7:12 AM, jm wrote:
> The process is still running and ops dont want to stop it. As soon as
> stops I'll try checkindex.
>
>
The process is still running and ops dont want to stop it. As soon as
stops I'll try checkindex.
Its created brand new with 2.4.1
On Thu, Nov 26, 2009 at 12:42 PM, Michael McCandless
wrote:
> I think you're using a JRE that has the fix for the issue found in
> LUCENE-1282.
>
> Can you run Check
I think you're using a JRE that has the fix for the issue found in LUCENE-1282.
Can you run CheckIndex on your index and post the output?
Was this index created from scratch on Lucene 2.4.1? Or, created from
an earlier Lucene version?
Mike
On Thu, Nov 26, 2009 at 6:03 AM, jm wrote:
> or are w
or are we really? I think we are on 1.6 update 14 right??
sorry Im lost right now on jdk version numbering
On Thu, Nov 26, 2009 at 12:01 PM, jm wrote:
> on second thought...I hadnt noticed the jdk numbers properly, we are
> using using b28, and JDK 6 Update 10 (b28) is the one fixing this...
>
>
on second thought...I hadnt noticed the jdk numbers properly, we are
using using b28, and JDK 6 Update 10 (b28) is the one fixing this...
ok forget this then
thanks!
On Thu, Nov 26, 2009 at 11:55 AM, jm wrote:
> Hi,
>
> Dont know if this should be here or in java-dev, posting to this one
> first
Hi,
Dont know if this should be here or in java-dev, posting to this one
first. In one of our installations, we have encountered an exception:
Exception in thread "Lucene Merge Thread #0"
org.apache.lucene.index.MergePolicy$MergeException:
org.apache.lucene.index.CorruptIndexException: docs out o
14 matches
Mail list logo
