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 <r...@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 >
