: Problem solved. We gave the index space five times its original size, just
: to be safe. Then the optimize finished without problems and without
: leaving deleted, yet still open files behind. During the optimize the
: index directory peaked at almost three times its size, and now,
: afterwards,
Hi again,
Problem solved. We gave the index space five times its original size, just
to be safe. Then the optimize finished without problems and without
leaving deleted, yet still open files behind. During the optimize the
index directory peaked at almost three times its size, and now,
afterwards,
Dominik,
Form my experiences with Solr, I have seen the index double its size during
an optimize.
I always keep my index directory in a partition that has at least its triple
size, so I have a margin for optimize and for natural doc quantity growth.
2009/1/16 Dominik Schramm
> On more thing th
On more thing that might help to identify the problem source (which I've
discovered just now) -- at the time the optimize "finished" (or broke
off), Tomcat logged the following:
r...@cms004:~# /opt/apache-tomcat-sba1-live/logs/catalina.2009-01-16.log
...
Jan 16, 2009 11:40:14 AM org.apache.solr.co
Hello,
we are running "Solr Implementation Version: 1.2.0 - Yonik - 2007-06-02
17:35:12" with "Lucene Implementation Version: build 2007-05-20" in a
Tomcat application server "Apache Tomcat/5.5.20" on a 64-bit Ubuntu 7.10.
For some time now (probably due to the continuous growth of the index,
whi
