Here is a weird architecture... We have a SOLR Master today, next to our database in our local data center. We do Solr replication to Amazon East and West coasts once the index is completed.
We would like to deploy Solr Cloud while leaving the master in place. 1. Local has SQL Server, and Solr Master. 2. We would like to replicate to EAST 2 machines, and WEST 2 machines. 3. The 2 machines on the East coast - we want to increase to 3, and use Zoo Keeper to keep the configs in sync with the Master local. And we would like to use Sharding/Collections to split the core into a collection across 3 machines for performance. Indexing can stay local. I understand that this is not normal, and maybe we can still use Master replication with Sharinding/or Solr Cloud ? ideas? -- Bill Bell billnb...@gmail.com cell 720-256-8076
