lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lance Norskog <goks...@gmail.com>
Subject Re: Sharing index files between multiple JVMs and replication
Date Fri, 06 Aug 2010 01:01:39 GMT
Oh yes, replication will not work for shared files. It is about making
your own copy from another machine.

There is no read-only option but there should be. The files and
directory can be read-only, I've done it. You could use the OS
permission system to enforce read-only. Then you can just do a
<commit> against the read-only instances, and this will reload the
index without changing it.

Lance

On Wed, Aug 4, 2010 at 10:42 AM, Kelly Taylor <wiredkel@yahoo.com> wrote:
> Is anybody else encountering these same issues; IF having a similar setup?  And
> is there a way to configure certain Solr web-apps as read-only (basically dummy
> instances) so that index changes are not allowed?
>
>
>
> ----- Original Message ----
> From: Kelly Taylor <wiredkel@yahoo.com>
> To: solr-user@lucene.apache.org
> Sent: Tue, August 3, 2010 5:48:11 PM
> Subject: Re: Sharing index files between multiple JVMs and replication
>
> Yes, they are on a common file server, and I've been sharing the same index
> directory between the Solr JVMs. But I seem to be hitting a wall when attempting
>
> to use just one instance for changing the index.
>
> With Solr replication disabled, I stream updates to the one instance, and this
> process hangs whenever there are additional Solr JVMs started up with the same
> configuration in solrconfig.xml  -  So I then tried, to no avail, using a
> different configuration, solrconfig-readonly.xml where the updateHandler was
> commmented out, all /update* requestHandlers removed, mainIndex locktype of
> none, etc.
>
> And with Solr replication enabled, the Slave seems to hang, or at least report
> unusually long time estimates for the current running replication process to
> complete.
>
>
> -Kelly
>
>
>
> ----- Original Message ----
> From: Lance Norskog <goksron@gmail.com>
> To: solr-user@lucene.apache.org
> Sent: Tue, August 3, 2010 4:56:58 PM
> Subject: Re: Sharing index files between multiple JVMs and replication
>
> Are these files on a common file server? If you want to share them
> that way, it actually does work just to give them all the same index
> directory, as long as only one of them changes it.
>
> On Tue, Aug 3, 2010 at 4:38 PM, Kelly Taylor <wiredkel@yahoo.com> wrote:
>> Is there a way to share index files amongst my multiple Solr web-apps, by
>> configuring only one of the JVMs as an indexer, and the remaining, as
> read-only
>> searchers?
>>
>> I'd like to configure in such a way that on startup of the read-only
> searchers,
>> missing cores/indexes are not created, and updates are not handled.
>>
>> If I can get around the files being locked by the read-only instances, I
> should
>> be able to scale wider in a given environment, as well as have less replicated
>> copies of my master index (Solr 1.4 Java Replication).
>>
>> Then once the commit is issued to the slave, I can fire off a RELOAD script
> for
>> each of my read-only cores.
>>
>> -Kelly
>>
>>
>>
>>
>>
>
>
>
> --
> Lance Norskog
> goksron@gmail.com
>
>
>
>
>



-- 
Lance Norskog
goksron@gmail.com

Mime
View raw message