No, that's not what I'm thinking at all. There would be _no_ replication configured. You'd just have two completely independent installations, one in each of your separate locations. The only communication path would be that somehow the original documents would need to get to both locations for indexing.
As far as each separate locations is concerned, any others don't exist. I suppose you could configure old-style replication, but then the remote data center would lag and you'd lose the NRT goodness etc. But that wouldn't be my first choice... As for your question about roles, it's hard to see how that fits. What are you envisioning would be different about the roles? SolrCloud is based upon the raw documents getting to each node and being indexed there. There's no notion of indexing the doc on one node and them moving the _results_ of the indexing process to the other replicas unless you eschew SolrCloud and just configure it as you would a 3.x system. Currently there are "leader" and "replica" roles, but all a leader does during indexing is route incoming documents appropriately (ones that belong in another shard are sent to the leader of that shard, and ones that belong in its shard to its replicas). Best Erick On Sun, Oct 14, 2012 at 12:19 PM, AlexeyK <lex.kudi...@gmail.com> wrote: > In other words, I would have to apply a mixture of modes: SolrCloud for each > location + old-style replication for mirroring. > BTW, I've seen a notion of 'role' in node cloud state. Is it in use or is > there for future extensions? Having 'indexer' and 'searcher' roles backed by > the infrastructure would help in certain scenarios I think. > > Alexey > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-distributed-architecture-considerations-tp4013594p4013616.html > Sent from the Solr - User mailing list archive at Nabble.com.
