Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Message-ID: <3FE84D20.60509@analog.com>
Date: Tue, 23 Dec 2003 14:11:44 +0000
From: Niall Gallagher <niall.gallagher@analog.com>
Reply-To: niall.gallagher@analog.com
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.5) Gecko/20031016
MIME-Version: 1.0
To: Lucene Users List <lucene-user@jakarta.apache.org>
Subject: Re: IndexWriter Problem
References: <3FE81CD7.2020701@analog.com> <3FE83FD6.4050809@analog.com>
 <DFD9FB53-354D-11D8-9188-000393A564E6@ehatchersolutions.com>
In-Reply-To: <DFD9FB53-354D-11D8-9188-000393A564E6@ehatchersolutions.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


 >> think I have resolved the problem. I was using Lucene to index 
several directories concurrently within
 >> the same JVM, and as far as I can tell Lucene cannot do coucurrent 
indexing. Is this correct ?

 > You can do it concurrently, but you must use the *same* IndexWriter 
instance on all threads.  

I was using different 'index' directories for each, it seems that there 
is some static resource that is not thread safe in some manner. For 
example my implementation went somthing like

for(int i = 0; i < 10; i++){
    new Thread(this).start();
}

public void run(){
   while(true){
       String path = queue.dequeue();
      
       if(isActive(path)){
          contuine;
       }
       activate(path);
       index(path,  new File(path, "index"));
   }
}

Should this work ? Because when I used it there was only ever one 
indexing task ever updating the index, that is, the last IndexWriter 
created was the only one updating its index directory.

Niall


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