[ 
https://issues.apache.org/jira/browse/SOLR-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259574#comment-13259574
 ] 

Mark Miller commented on SOLR-3397:
-----------------------------------

bq. Since SolrCloud takes this functionality over completely, it seems like 
replication needs to be made smart enough to disable itself if running under 
SolrCloud.

SolrCloud does not take this functionality over - it uses it. The example 
replication handler given in the example solrconfig.xml is sufficient. Some 
other config might make sense (say you want to enable basic auth or 
compression), while others should be left alone - eg you don't want to 
configure a node as a slave most likely.

SolrCloud takes advantage of the existing replication functionality and pass 
parameters about who to poll from and when - you can't disable it - we might 
just do some conf checks and print warnings and or fail depending on config 
that is found - but in some cases their might be legit reasons to alter config 
in ways we don't anticipate depending on what you might be trying to setup.
                
> 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

Reply via email to