Hi, As far as I understand, SolrCloud eliminates the master-slave specifics, and automates both update and search seamlessly. What should I take into account configuring SolrCloud for a large customer with multiple physical locations? I mean, for older Solr I would define master 'close to the data' with batch replication to the search server (slave). I would have several such slaves for different geographical locations as well. How can I ensure (if at all) that search queries do not cross geographical boundaries? As far as I understand, SolrCloud routes to any arbitrary active replica. How can I control the indexing process so that the update request is routed to the closest server? If SolrCloud accidentally elects some remote replica as a current leader, the indexing process will deteriorate due to networking issues; moreover, the update requests will be also bounced back across the network as a part of the online replication process.
Do I miss something fundamental in my assumptions/understanding of SolrCloud features? Thanks a lot, Alexey -- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-distributed-architecture-considerations-tp4013594.html Sent from the Solr - User mailing list archive at Nabble.com.
