OK then this should be fine. That single machine, on receiving a JMS
message, should use a single IndexWriter for making changes to the
index (ie, it should not try to open a 2nd IndexWriter while a
previous one is still working on a previous message).
Mike
Sandeep K wrote:
Thanks a lot Mike,
There will be only one machine which uses IndexWriter and its the
JMS server. This server will first create the file in the physical
file
system(its Linux)
and then index the saved file.
Michael McCandless-2 wrote:
Sandeep K wrote:
Hi all..
I had a question related to the write locks created by Lucene.
I use Lucene 2.3.2. Will this newwer version create locks while
indexing as
older ones?
or is there any other way that lucene handles its operations?
It still creates write locks, which are used to ensure only one
writer
is changing the index at a time.
And my another doubt is that i use JMS for lucene indexing.
My App server will not do indexing but will pass the needed data for
indexing to the JMS server.
will there be any problem in indexing as its asynchronous?
plz help me..
Will there be multiple machines that might open an IndexWriter and do
indexing, on receiving messages from the JMS server?
What filesystem is being used to share access to the index?
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Lucene-write-locks-tp18604932p18607685.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
