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, which is now roughly 40 GB in size) we experience a problem with deleted but still growing index files: r...@cms004:~# lsof | grep deleted ... java 10601 root 84u REG 8,9 237359104 2981966 /opt/solr1/data/index/_3tmy9.frq (deleted) java 10601 root 85u REG 8,9 120507392 2981967 /opt/solr1/data/index/_3tmy9.prx (deleted) java 10601 root 86u REG 8,9 14528512 2981968 /opt/solr1/data/index/_3tmy9.tis (deleted) java 10601 root 87u REG 8,9 233472 2981971 /opt/solr1/data/index/_3tmy9.tii (deleted) ... r...@cms004:~# ps -fp 10601 UID PID PPID C STIME TTY TIME CMD root 10601 1 82 Jan15 pts/2 20:37:04 /usr/lib/jvm/java-1.5.0-sun-1.5.0.13/bin/java -Djava.awt.headless=true - r...@cms004:~# During the runs of the optimize.pl script (daily at night) the number of files marked as deleted increases and drops again, but not to zero! Several large files always remain even after the optimizer finished (the lsof snapshot above is from after an optimize run). But even more important is the fact that the Tomcat process still writes to them, eventually filling up the partition. The only solution right now is to restart the Tomcat process once a day. This is not super critical because we run a staging environment, but it's a nuisance. I've noticed that the commit preceding the optimize always fails: 2009/01/16 12:08:01 started by d 2009/01/16 12:08:01 command: /opt/solr1/bin/commit 2009/01/16 12:08:04 commit request to Solr at http://localhost:8083/solr1/update failed: 2009/01/16 12:08:04 <?xml version="1.0" encoding="UTF-8"?> <response> <lst name="responseHeader"><int name="status">0</int><int name="QTime">2423</int></lst> </response> 2009/01/16 12:08:04 failed (elapsed time: 3 sec) What can I do about this? Is this a known phenomenon in version 1.2.0 or with Tomcat etc. and has it been solved in subsequent versions? I couldn't find any specific hints at this in the changelogs. An upgrade would be untrivial and time-consuming, so I would like to make sure that the problem will go away afterwards. BTW: Danilo Fantinato described supposedly the same problem on Thu, 27 Sep 2007 16:37:01 GMT, (when the version we are still using was more or less the current one) the subject was "Problem with handle hold deleted files" -- there was no reply. See here: http://www.nabble.com/Problem-with-handle-hold-deleted-files-td12925293.html Thanks in advance for any help. Dominik
