Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 1372 invoked from network); 31 Mar 2007 23:09:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Mar 2007 23:09:37 -0000 Received: (qmail 7440 invoked by uid 500); 31 Mar 2007 23:09:38 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 7396 invoked by uid 500); 31 Mar 2007 23:09:38 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 7385 invoked by uid 99); 31 Mar 2007 23:09:38 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Mar 2007 16:09:38 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nileshbansal@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Mar 2007 16:09:28 -0700 Received: by ug-out-1314.google.com with SMTP id k40so1283546ugc for ; Sat, 31 Mar 2007 16:09:07 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=rcnxY0UFZxbLZTGiInWhSelJV6R886PnKwQyBlK7N8YzjNVQ7spqhURG1WuFfX9+fv70VruxlNRLv/E7EVO4vtLpJZwPmugCcajkIoujkbrmfNUWLD5iyPWO/UZAC2xZVL26H5VHUuCYIq+SRNCu4VEuljiSaNtSS7U/DM+45X8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=tSSbxSPup2rsLsDY+a/aAKPGYE0n5zwRlSVdaJS2I6B4orYkFfh6u5g6pdlvwRGcAmTxlGbmXxQQiR1PwV8wZMX/2nG0XFq5RBXBxoklAlvAZpkA0GdRbvrp82CPP/fqHoWbHLCD+t8O3nSdm8qC2BuJZh+7i5uujU6xZjQksBU= Received: by 10.78.158.11 with SMTP id g11mr1284474hue.1175382547077; Sat, 31 Mar 2007 16:09:07 -0700 (PDT) Received: by 10.78.52.2 with HTTP; Sat, 31 Mar 2007 16:09:06 -0700 (PDT) Message-ID: Date: Sat, 31 Mar 2007 19:09:06 -0400 From: "Nilesh Bansal" To: java-user@lucene.apache.org Subject: Lock files in a read-only application MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Hi all, We have a web-based application that searches a large lucene index. This application only creates object of type IndexSearcher only (and no IndexWriters) for searching the index. After the application runs for some time (a few hours), I can see lock files in the temp directory of the form /opt/tomcat/temp/lucene-5f77ffdc821b3f8e861949e9ecc35a53-commit.lock The temp dir is set to /opt/tomcat/temp/ as we are using tomcat. Since the application is read-only, there is no point in it using the lock files. These lock files are creating a lot of trouble for me, as their presence leads to a lock obtained timeout in other threads. It seems like a bug in lucene. The index is updated be a separate process independent of the web-application once in a while. Currently I am using an independent shell script that checks for the temp dir for lock files every few seconds and deletes the lock files if any (to prevent a lock obtained timeout in other threads). Any help will be appreciated. thanks Nilesh Bansal. http://queens.db.toronto.edu/~nilesh/ --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org