On Mon, Nov 30, 2009 at 2:34 PM, Michael McCandless
<luc...@mikemccandless.com> wrote:
> On Mon, Nov 30, 2009 at 7:22 AM, jm <jmugur...@gmail.com> 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.setMaxFieldLength(maxFieldLength);
>>        writer.setMergeFactor(10);
>>        writer.setRAMBufferSizeMB(10);
>>        writer.setUseCompoundFile(true);
>>        writer.setTermIndexInterval(512);
>
> All normal.  The 512 terms index interval is interesting though --
> that's not a setting most people tweak.  I can't think how it could
> lead to what you're seeing though...

its to decrease memory see
http://old.nabble.com/possible-to-disable-internal-caching--to8968048.html

>
>> In this production environment only a single thread was indexing. No
>> addIndexes() is used. In some ocassions yes write.lock might be
>> deleted by code.
>
> Removing the write.lock when you shouldn't is a recipe for disaster --
> is there any chance you removed it when a writer was in fact still
> active?
No that was not the case, for sure.

>
>> I have added infoStream to stdout in my code so in the future we would
>> run this with debug on.
>
> OK excellent.  Post back with the output if/when it happens... thanks!
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Reply via email to