Re: SolrCloud: read only node

2013-11-04 Thread Erick Erickson
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 wrote: > F***, this is the answer, I was

Re: SolrCloud: read only node

2013-11-04 Thread Uwe Reh
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/slav

Re: SolrCloud: read only node

2013-11-04 Thread 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 in

SolrCloud: read only node

2013-11-04 Thread Uwe Reh
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 no