lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Albert <j.alb...@data-in-motion.biz>
Subject forceMerge(1) grows index and does not shrink back
Date Fri, 16 Jan 2015 13:57:02 GMT
Hi,

because we have constant updates on our index, we can't really close the 
index from time to time. Therefore we decided to trigger forceMerge  
when the traffic is lowest, the clean up.

On our development laptops (Windows and Linux) it works as expected, but 
on the real Servers we have some wired behaviour.

Scenario:

We create a fresh index and populate it. This results in an index with a 
size of 2 GB. If we rigger forceMerge(1) and a commit() afterwards for 
this index, the index grows over the next 10 minutes to 6 GB and does 
not shrink back. During the whole process no reader is opened on the index.
If I try the same stunt with the same data on my Windows Laptop, it does 
nothing at all and finishes after a few ms.

Any Ideas?

Technical details:
We use an MMapDirectory and the Server is a Debian7 Kernel 3.2 in a KVM. 
The file system is Ext4.

Thx,

Jürgen Albert.

-- 
Jürgen Albert
Geschäftsführer

Data In Motion UG (haftungsbeschränkt)

Kahlaische Str. 4
07745 Jena

Mobil:  0157-72521634
E-Mail: j.albert@datainmotion.de
Web: www.datainmotion.de

XING:   https://www.xing.com/profile/Juergen_Albert5

Rechtliches

Jena HBR 507027
USt-IdNr: DE274553639
St.Nr.: 162/107/04586


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


Mime
View raw message