Lucene search result no stable

[Ardor Wei <ar...@yahoo.com>]

Hi, experts,

Our application pulls data out of DB and write as
lucene document every 5 minutes. We use a loop to keep
updating document. But we only use 1 writing thread
and always closes IndexWriter once we finish writing.
Unfortunately, we always got IOException and
FileNotFoundException ( I guess there is some problem
with the lock time setting inside Lucene, though I am
not sure). Our IndexSearcher doesn't do deletion, so
it is thread safety. But the problem is we sometimes
get the results (e.g 10) we expect, sometimes we get
nothing. I traced with other engineers through our
code using Lucene. It looks like it is pretty straight
and correct. But the exceptions keep being thrown and
I think the unstable search result is also related to
these exceptions. 

What might be the problem? How to solve it?
Any suggestion or idea will be appreciated.

Thanks.

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

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

Re: Lucene search result no stable

[Ardor Wei <ar...@yahoo.com>]

Thanks, Morus, Our real web server, database and the
directory Lucene writes in physically share the same
computer. File system is Win FAT.

For java.io.tmpdir, do you mean I need to explicitly
set it as system environment variable or set it in a
property file?

Thanks again!

--- Morus Walter <mo...@tanto-xipolis.de>
wrote:
> Ardor Wei writes:
> > 
> > What might be the problem? How to solve it?
> > Any suggestion or idea will be appreciated.
> > 
> The only problem with locking I saw so far is that
> you have
> to make sure that the temp dir is the same for all
> applications.
> Lucene 1.3 stores it's lock in the directory that is
> defined by the
> system property java.io.tmpdir.
> I had one component running under tomcat and one
> from the shell
> and they used different temp dirs which is fatal in
> this case.
> 
> Apart from this it depends pretty much on your
> environment.
> I'm using lucene on linux on local filesystems.
> Other operating
> systems or network filesystems may influence
> locking.
> 
> Morus
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> lucene-user-help@jakarta.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/

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

Re: Lucene search result no stable

[Morus Walter <mo...@tanto-xipolis.de>]

Ardor Wei writes:
> 
> What might be the problem? How to solve it?
> Any suggestion or idea will be appreciated.
> 
The only problem with locking I saw so far is that you have
to make sure that the temp dir is the same for all applications.
Lucene 1.3 stores it's lock in the directory that is defined by the
system property java.io.tmpdir.
I had one component running under tomcat and one from the shell
and they used different temp dirs which is fatal in this case.

Apart from this it depends pretty much on your environment.
I'm using lucene on linux on local filesystems. Other operating
systems or network filesystems may influence locking.

Morus

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