On 3/25/2014 10:42 AM, Software Dev wrote:
I see that by default in SolrCloud that my collections are
replicating. Should this be disabled in SolrCloud as this is already
handled by it?
From the documentation:
"The Replication screen shows you the current replication state for
the named core you have specified. In Solr, replication is for the
index only. SolrCloud has supplanted much of this functionality, but
if you are still using index replication, you can use this screen to
see the replication state:"
I just want to make sure before I disable it that if we send an update
to one server that the document will be correctly replicated across
all nodes. Thanks
The replication handler must be configured for SolrCloud to operate
properly ... but not in the way that you might think. This is a source
of major confusion for those who are new to SolrCloud, especially if
they already understand master/slave replication.
During normal operation, SolrCloud does NOT use replication.
Replication is ONLY used to recover indexes. When everything is working
well, recovery only happens when a Solr instance starts up.
Every Solr instance will be a master. If that Solr instance has *EVER*
(since the last instance start) replicated its index from a shard
leader, it will *also* say that it is a slave. These are NOT indications
that a replication is occurring, they are just the current configuration
state of the replication handler.
You can ignore everything you see on the replication tab if you are
running SolrCloud. It only has meaning at the moment a replication is
happening, and that is completely automated by SolrCloud.
Thanks,
Shawn
