How do you handle commits to the index? By that, I mean that Solr recreates its searcher when you issue a commit, but only for the system that does the commit. Wouldn't you be left with searchers on the other machines that are stale?
- Charlie -----Original Message----- From: Matthew Runo [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 12:18 PM To: solr-user@lucene.apache.org Subject: Re: Shared index base I hope so. I've found that every once in a while Solr 1.2 replication will die, from a temp-index.... file that seems to ham it up. Removing that file on all the servers fixes the issue though. We'd like to be able to point all the servers at an NFS location for their index files, and use a single server to update it. Thanks! Matthew Runo Software Developer Zappos.com 702.943.7833 On Feb 26, 2008, at 9:39 AM, Alok Dhir wrote: > Are you saying all the servers will use the same 'data' dir? Is > that a supported config? > > On Feb 26, 2008, at 12:29 PM, Matthew Runo wrote: > >> We're about to do the same thing here, but have not tried yet. We >> currently run Solr with replication across several servers. So long >> as only one server is doing updates to the index, I think it should >> work fine. >> >> >> Thanks! >> >> Matthew Runo >> Software Developer >> Zappos.com >> 702.943.7833 >> >> On Feb 26, 2008, at 7:51 AM, Evgeniy Strokin wrote: >> >>> I know there was such discussions about the subject, but I want to >>> ask again if somebody could share more information. >>> We are planning to have several separate servers for our search >>> engine. One of them will be index/search server, and all others >>> are search only. >>> We want to use SAN (BTW: should we consider something else?) and >>> give access to it from all servers. So all servers will use the >>> same index base, without any replication, same files. >>> Is this a good practice? Did somebody do the same? Any problems >>> noticed? Or any suggestions, even about different configurations >>> are highly appreciated. >>> >>> Thanks, >>> Gene >> >
