chanchitodata wrote:
I actually dont hit OOM, The memory gets 100% full and the JVM hangs.
Is it GC'ing during this hang? Can you try reducing your heap size
down alot and see if the GC runs faster? (Or, if you can provoke an
OOM).
How large is your heap now?
Independently what type
inking that it was Compass the held on to something in memory but
>>>> we have
>>>> come into conclusion that it must be Lucene that keeps holding on
>>>> the the
>>>> memory.
>>>>
>>>> I have read the thread
>>>> http:
834
and tried to divide my index into smaller parts but with the same
result.
The index contains about 1.5Gb with around 2.7 Million documents and
aprox.
30 Fields.
/Rodrigo
--
View this message in context:
http://www.nabble.com/Memory-Eaten-up-by-TermInfo-Instances-in-Lucene-2.4-tp21913262p2191
maller parts but with the same
>> result.
>>
>> The index contains about 1.5Gb with around 2.7 Million documents and
>> aprox.
>> 30 Fields.
>>
>> /Rodrigo
>> --
>> View this message in context:
>> http://www.nabble.com/Memory-Eaten-up
the same
result.
The index contains about 1.5Gb with around 2.7 Million documents and
aprox.
30 Fields.
/Rodrigo
--
View this message in context:
http://www.nabble.com/Memory-Eaten-up-by-TermInfo-Instances-in-Lucene-2.4-tp21913262p21913262.html
Sent from the Lucene - Java Users mailing list ar
ocuments and aprox.
30 Fields.
/Rodrigo
--
View this message in context:
http://www.nabble.com/Memory-Eaten-up-by-TermInfo-Instances-in-Lucene-2.4-tp21913262p21913262.html
Sent from the Lucene - Java Users mailing list archive at Na
