[
https://issues.apache.org/jira/browse/SOLR-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776264#comment-13776264
]
Erick Erickson commented on SOLR-3397:
--------------------------------------
Comments from dev list discussion:
Erick:
Let's say a configuration is running SolrCloud _and_ has <lst
name="master"> or <lst name="slave"> bits defined in the replication
handler. Is it valid? Taken care of? Is it worth a JIRA to barf if we
detect that condition?
Because it strikes me as something that's at worst undefined behavior,
at best ignored and somewhere in the middle does replications as well
as peer synchs as well as distributed updates.
Under any circumstances it doesn't seem like the user is doing the right thing.
Shawn:
Initial thought: Yes, detect and explode.
Second thought: Allowing replication config for the expert user (possibly for
backup purposes) might be useful.
Third thought: Yes, detect and explode. If someone wanted to write an
application that used the handler as a direct API rather than through
solrconfig.xml configuration, that would work with no problem. SolrCloud
basically requires that the /replication handler be enabled, but not configured.
Is the replication API fully documented anywhere? It might be nice to provide
a skeletal example java application that talks to the replication API for
simple index backup purposes. It would be particularly nice if it used
CloudSolrServer (or the ZK client classes) and showed how to back up and
restore multiple shards. If I had any idea how to write such an application, I
would have already gotten started on it.
> 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-ALPHA
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
