Hi,
I am getting the following OOM consistently whenever the index is opened . Is
it because now the index is holding too many terms ? Our application ( that has
Lucene 2.9.3 ) already has reached 1.8G of virtual memory.
Is there a way I can avoid OOM during IndexReader open because of too many
Hi Uwe,
I ran my setup with JDK1.6.0_29 .
Exception that I get -
2011-11-15 23:54:24,518 [MC:10.10.176.148-1321429549689-426 FS:emag_393219_0]
ERROR indexer - MergeWithFiler: MC: 393219, shard 0, guid
10.10.176.148-1321429549689-426: Error in addIndex()/kazMaybeMerge():
/sideline/fs_393219/ca
Thanks Uwe for your comments.
Few points to note for our setup -
1) At any time only one thread will be adding index and merging with the final
index. Two threads will not concurrently be doing addindex and merge.
2) In the current setup where I am seeing the corruption, only one process is
work
We are seeing Index corruption very often with version 2.9.3. Our indexing
process is on Linux ( centos 5 ). Index is created on a mounted drive which is
a shared drive from Windows 2008 server running in a VM. We generally see index
corruption in merge or optimize after indexing runs continuous
