Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <00c001c495b5$5288c210$aa87a8c0@ppeddi>
From: "Praveen Peddi" <ppeddi@contextmedia.com>
To: "Lucene Users List" <lucene-user@jakarta.apache.org>,
	<nsh@bayt.net>
References: <D98ADD74A4E07445A943A90A184B51993792E4@zebedee.magus.co.uk>
Subject: Re: Moving from a single server to a cluster
Date: Wed, 8 Sep 2004 11:05:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

We went thru the same scenario as yours. We recently made our application
clsuterable and I wrote our own version of jdbc directory (similar to the
SQLDirectory posted by someone) with our own caching. It was great for
searching for indexing had become a real bottleneck. So we have decided to
move back to file system for non-clustered apps. I am still trying to figure
the best way (whether using a RemoteSearcher or manage multiple index). I
already tried multiple index and we didn't really like the solution of
maintaining multiple copies. It requires more space, more maintaineance, all
index needs to be in sync etc.

I will be glad if I can get the best answer for this. Did anyone try
RemoteSearchable and how is it compared to multiple index solution?

 Nader: I would appreciate if you can send me the docs.

Praveen

----- Original Message ----- 
From: "David Townsend" <david.townsend@magus.co.uk>
To: "Lucene Users List" <lucene-user@jakarta.apache.org>; <nsh@bayt.net>
Sent: Wednesday, September 08, 2004 10:42 AM
Subject: RE: Moving from a single server to a cluster


Would it be cheeky to ask you to post the docs to the group?  It would be
interesting to read how you've tackled this.

-----Original Message-----
From: Nader Henein [mailto:nsh@bayt.net]
Sent: 08 September 2004 13:57
To: Lucene Users List
Subject: Re: Moving from a single server to a cluster


Hey Ben,

We've been using a distributed environment with three servers and three
separate indecies for the past 2 years since the first stable Lucene
release and it has been great, recently and for the past two months I've
been working on a redesign for our Lucene App and I've shared my
findings and plans with Otis, Doug and Erik, they pointed out a few
faults in my logic which you will probably come across soon enough that
mainly have to do with keeping you updates atomic (not too hard) and
your deletes atomic (a little more tricky), give me a few days and I'll
send you both the early document and the newer version that deals
squarely with Lucene in a distributed environment with high volume index.

Regards.

Nader Henein

Ben Sinclair wrote:

>My application currently uses Lucene with an index living on the
>filesystem, and it works fine. I'm moving to a clustered environment
>soon and need to figure out how to keep my indexes together. Since the
>index is on the filesystem, each machine in the cluster will end up
>with a different index.
>
>I looked into JDBC Directory, but it's not tested under Oracle and
>doesn't seem like a very mature project.
>
>What are other people doing to solve this problem?
>
>
>

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


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


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