Hi,
I found my problem,
The remoteServer index wasn't closed expectedly.
Also after reopen the remoteServer searcher,
the client side searcher also should reconnected.
Thanks.
Youngho
- Original Message -
From: Youngho Cho [EMAIL PROTECTED]
To: Lucene Users List lucene-user@jakarta.apache.org
Sent: Friday, February 18, 2005 1:38 PM
Subject: Re: ParrellelMultiSearcher Question
Hello Erik,
Yes. I read it.
And tried to close the remote index from remote server and client both.
But when I search again,
I received the
IOException: Bad file descriptor
Maybe I am wrong.
Is there any demo sample ?
Thanks.
Youngho
- Original Message -
From: Erik Hatcher [EMAIL PROTECTED]
To: Lucene Users List lucene-user@jakarta.apache.org
Sent: Friday, February 18, 2005 11:47 AM
Subject: Re: ParrellelMultiSearcher Question
If you close a Searcher that goes through a RemoteSearchable, you'll
close the remote index. I learned this by experimentation for Lucene
in Action and added a warning there:
http://www.lucenebook.com/search?query=RemoteSearchable+close
On Feb 17, 2005, at 8:27 PM, Youngho Cho wrote:
Hello,
Is there any pointer
how closing an index and how the server deals with index updates
for using ParrellelMultiSearcher with built in RemoteSearcher ??
Need your help.
Thanks,
Youngho
- Original Message -
From: Youngho Cho [EMAIL PROTECTED]
To: Lucene Users List lucene-user@jakarta.apache.org
Sent: Thursday, February 17, 2005 6:29 PM
Subject: ParrellelMultiSearcher Question
Hello,
I would like to use ParrellelMultiSearcher with few RemoteSearchables.
If one of the remote server is down,
Can I parrellelMultiSearcher set close() and
make new ParrellelMultiSearcher with other live RemoteSearchables ?
Thanks.
Youngho
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
