well, you could probably do what you want. Go ahead and index on the "super
cool AWS instance", just don't bring the replicas up yet. All the indexing
is going to this machine. Once your index is constructed, bring up
replicas. Old-style replication will take place and you should be off to
the race
Jason,
Thanks for raising it!
Erick,
That's what I want to discuss for a long time. Frankly speaking, the
question is:
if old-school (master/slave) search deployments doesn't comply to vision by
SolrCloud/ElasticSearch, does it mean that they are wrong?
Let me enumerate kinds of 'old-school sear
First, forget about master/slave with SolrCloud! Leaders really exist to
resolve conflicts, the old notion of M/S replication is largely irrelevant.
Updates can go to any node in the cluster, leader, replica, whatever. The
node forwards the doc to the correct leader based on a hash of the
, which
