You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Uwe Reh <re...@hebis.uni-frankfurt.de> on 2013/11/04 13:34:19 UTC
SolrCloud: read only node
Hi,
as service provider for libraries we run a small cloud (1 collection, 1
shard, 3 replicas). To improve the local reliability we want to offer
the possibility to set up own local replicas.
As fas as I know, this can be easily done just by adding a new node to
the cloud. But the external node shouldn't be able to do any changes on
the index.
Is there a cheap way to restrict a node of a SolrCloud into a read only
modus?
Is it a better idea, to do legacy replication from one node (master) to
an external slave?
Uwe
Re: SolrCloud: read only node
Posted by Erick Erickson <er...@gmail.com>.
Well, I do have to question why you need to do anything.
Just don't send updates to the remote machines......
But do remember that all nodes in SolrCloud can be equal,
which is one of the points.....
FWIW,
Erick
On Mon, Nov 4, 2013 at 10:34 AM, Uwe Reh <re...@hebis.uni-frankfurt.de> wrote:
> F***, this is the answer, I was afraid of. ;-)
> I hoped, there could be anything, similar to http://zookeeper.apache.org/
> doc/trunk/zookeeperObservers.html.
>
> Nevertheless, thank you.
> Uwe
>
> Am 04.11.2013 14:14, schrieb Erick Erickson:
>
> In this situation, I'd consider going with the older master/slave
>> setup. The problem is that in SolrCloud, you have a lot of chatter
>> back and forth. Presumably the connection to your local instances
>> is rather slow, so if you're adding data to your index, each and
>> every add has to be communicated individually to the remote node.
>>
>> But no, there's no good way in SolrCloud to make a node "read only".
>> Actually, that doesn't really make sense in the solr cloud world since
>> each node maintains its own index, does its own indexing, etc. So
>> each node _must_ be able to change the Solr index it uses.
>>
>> FWIW,
>> Erick
>>
>>
>
Re: SolrCloud: read only node
Posted by Uwe Reh <re...@hebis.uni-frankfurt.de>.
F***, this is the answer, I was afraid of. ;-)
I hoped, there could be anything, similar to
http://zookeeper.apache.org/doc/trunk/zookeeperObservers.html.
Nevertheless, thank you.
Uwe
Am 04.11.2013 14:14, schrieb Erick Erickson:
> In this situation, I'd consider going with the older master/slave
> setup. The problem is that in SolrCloud, you have a lot of chatter
> back and forth. Presumably the connection to your local instances
> is rather slow, so if you're adding data to your index, each and
> every add has to be communicated individually to the remote node.
>
> But no, there's no good way in SolrCloud to make a node "read only".
> Actually, that doesn't really make sense in the solr cloud world since
> each node maintains its own index, does its own indexing, etc. So
> each node _must_ be able to change the Solr index it uses.
>
> FWIW,
> Erick
>
Re: SolrCloud: read only node
Posted by Erick Erickson <er...@gmail.com>.
In this situation, I'd consider going with the older master/slave
setup. The problem is that in SolrCloud, you have a lot of chatter
back and forth. Presumably the connection to your local instances
is rather slow, so if you're adding data to your index, each and
every add has to be communicated individually to the remote node.
But no, there's no good way in SolrCloud to make a node "read only".
Actually, that doesn't really make sense in the solr cloud world since
each node maintains its own index, does its own indexing, etc. So
each node _must_ be able to change the Solr index it uses.
FWIW,
Erick
On Mon, Nov 4, 2013 at 7:34 AM, Uwe Reh <re...@hebis.uni-frankfurt.de> wrote:
> Hi,
>
> as service provider for libraries we run a small cloud (1 collection, 1
> shard, 3 replicas). To improve the local reliability we want to offer the
> possibility to set up own local replicas.
> As fas as I know, this can be easily done just by adding a new node to the
> cloud. But the external node shouldn't be able to do any changes on the
> index.
>
> Is there a cheap way to restrict a node of a SolrCloud into a read only
> modus?
> Is it a better idea, to do legacy replication from one node (master) to an
> external slave?
>
>
> Uwe
>