Re: Multi process writer access to an index

2008-03-24 Thread Otis Gospodnetic
uld be best to check on the Lucene.Net list. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message From: Eran Sevi <[EMAIL PROTECTED]> To: java-user@lucene.apache.org Sent: Wednesday, March 19, 2008 10:10:46 AM Subject: Re: Multi process writer acc

Re: Multi process writer access to an index

2008-03-19 Thread Eran Sevi
Sorry for any duplicate posts. Actually I'm using the latest "final" Lucene.Net and I hope this problem is not unique to this version. The OS is windows, FS - NTFS. Here's an example of what I do in each process (which may reside on a different computer): writer = new IndexWriter(

Re: Multi process writer access to an index

2008-03-19 Thread Michael McCandless
Are you using multiple computers? Probably what's happening is: because older versions of Lucene store the lock file in the /tmp directory by default, multiple computers sharing an index will be able to open multiple writers because they have their own /tmp directories. They don't see eac

Multi process writer access to an index

2008-03-19 Thread Eran Sevi
Hi, I'm trying to write to a specific index from several different processes and encounter problems with locked files (deletable for example). I don't perform any specific locking because as I understand it there should be file-specific locking mechanism used by lucene API. This doesn't seem to be

Re: Multi process writer access to an index

2008-03-19 Thread Erick Erickson
You'll get more meaningful answers if you provide some details: Things that come to mind: op system (windows? *nix?) file system (NFS? local? NTFS?) An example of the error you receive (a stack trace would be good). The code you're executing when you get the error. Imagine you're trying to adv

Multi process writer access to an index

2008-03-19 Thread Eran Sevi
Hi, I'm trying to write to a specific index from several different processes and encounter problems with locked files (deletable for example). I don't perform any specific locking because as I understand it there should be file-specific locking mechanism used by lucene API. This doesn't seem to