We also run our sites in an environment where we have multiple
load-balanced web servers. Our solution is as follows:

We have an indexing server, which has an app running on it to
periodically create and update indexes. This then *pushes* the indexes
out to shares on the web servers. The web site code then reads from it's
own local disk. This solution means there is only one app hitting the
data store (sql database in our case) but there will not be any
performance issues from multiple apps reading the same index across the
network.  It's actually a little more complicated than this as in order
to get around issues with changing the index mid-web-request, we create
new directories with new versions of indexes (or updates) and update an
xml file that points to these.

If anyone wants to discuss our solution futher feel free to contact me.

Thanks,

Pete

www.stylefinder.com
www.vogue.co.uk
www.glamourmagazine.co.uk

-----Original Message-----
From: brydon [mailto:[EMAIL PROTECTED] 
Sent: 14 August 2007 17:09
To: [email protected]
Subject: Re: lucene.net on UNC share

Can anyone comment as to whether storing the index on a UNC share would
likely be problematic? We haven't been able to fully diagnose the issues
we're seeing so I'm concerned about making these changes and not
resolving our current issues.

As well, I believe we're running an older release. Where can we grab the
most recent stable build from?

thanks,
brydon





Nathan Hoover wrote:
> We've installed the indices on a separate app server and handle the 
> search requests via Remoting.
>
> There are also some remote search classes within the Lucene.NET 
> package, but I have yet to use them.
>
> N
>
> -----Original Message-----
> From: brydon [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 14, 2007 6:54 AM
> To: lucene user list
> Subject: lucene.net on UNC share
>
> Hey all,
>
> What is the common pattern for implementing Lucene.net in an 
> environment with multiple, load balanced web servers?
>
> We've been attempting to store the index and lock files on a UNC 
> share, however, we seem to be continually running into invalid results

> in the index. As well, we get "cannot create directory" errors that 
> occur somewhat randomly, or at least we haven't established the
pattern yet.
>
> Thanks, in advance, for any advice.
>
> thanks,
> brydon
>
> {*} Band of Coders
>
> http://bandOfCoders.com
> http://shiftMode.com
> 519.489.0116
>
>   

The information contained in this e-mail is of a confidential nature and is 
intended only for the addressee.  If you are not the intended addressee, any 
disclosure, copying or distribution by you is prohibited and may be unlawful.  
Disclosure to any party other than the addressee, whether inadvertent or 
otherwise, is not intended to waive privilege or confidentiality.  Internet 
communications are not secure and therefore Conde Nast does not accept legal 
responsibility for the contents of this message.  Any views or opinions 
expressed are those of the author.

Company Registration details:
The Conde Nast Publications Ltd
Vogue House
Hanover Square
London W1S 1JU

Registered in London No. 226900

Reply via email to