You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/12 00:29:18 UTC

[jira] [Commented] (SOLR-3397) Insure that Replication and Solr Cloud are compatible

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

ASF subversion and git services commented on SOLR-3397:
-------------------------------------------------------

Commit 1540881 from [~erickoerickson] in branch 'dev/trunk'
[ https://svn.apache.org/r1540881 ]

SOLR-3397: Insure that replication and SolrCloud are compatible. Actually, just log a warning if SolrCloud is detected and master or slave is configured in solrconfig.xml

> 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
>            Assignee: 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 was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org