[
https://issues.apache.org/jira/browse/SOLR-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259581#comment-13259581
]
Erick Erickson commented on SOLR-3397:
--------------------------------------
I phrased it poorly, I'm aware that SolrCloud uses replication as needed.
My base question here is are we sure that if a user has a classic master/slave
setup _and_ is running SolrCloud, do they play nice together? So a slave polls
the master, and new segments are moved to the slave (classic). Meanwhile, the
master may or may not be the leader. The updates may have been received already
via the leader forwarding the requests. Does this all behave well?
And if the leader goes down, a new leader is elected and classic replication
does what?
It seems like the replication handler polling should just be disabled in the
SolrCloud world or is this all "just handled" today?
We've seen problems in the past where people configure a classic master/slave
setup then merrily index to both machines, replication can get all confused.
I'm making sure this has been handled or at least is flagged as something to
check.
And, yes, "they shouldn't do that". If we can put in a low-cost way to insure
this it might save people grief. And people will no doubt be upgrading from 3.x
at some point, moving their solrconfig files if nothing else....
But as I said, I may be seeing something that's not there in which case we can
close this as "silly boy is hallucinating again"...
> Insure that Replication and Solr Cloud are compatible
> -----------------------------------------------------
>
> Key: SOLR-3397
> URL: https://issues.apache.org/jira/browse/SOLR-3397
> Project: Solr
> Issue Type: Improvement
> Components: replication (java), SolrCloud
> Affects Versions: 4.0
> Reporter: Erick Erickson
>
> There has been at least one report of an early-adopter having replication (as
> in master/slave) configured with SolrCloud and having very odd results.
> Experienced Solr users could reasonably try this (or just have their
> configurations from 3.x Solr installations hanging around). Since SolrCloud
> takes this functionality over completely, it seems like replication needs to
> be made smart enough to disable itself if running under SolrCloud.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
