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