You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2013/04/01 23:57:15 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=13619222#comment-13619222 ]
Shawn Heisey commented on SOLR-3397:
------------------------------------
I was planning to file a feature request for something that the Gluster project calls geo-replication. Would that fall under this issue, or should it be a new one?
With this feature, you would have two semi-independent SolrCloud setups, one of which would replicate from the other. Ideally, there would be no master or slave - either the replication would work in both directions, or a higher-level leader election would take place.
The driving force behind this feature is a user that wants to have a SolrCloud setup that is fully redundant between two data centers and can remain operational in the event of an entire data center going down. I'm not aware of a way to build a zookeeper ensemble in two locations that can always guarantee a working cluster without split-brain. Also, there is the fact that each update must be sent to all shards/replicas at the same time, which can be problematic when half of them are on a connection with high latency. If synchronizing the two clouds happens on a longer interval than the indexing, latency is less of a problem.
I'm sure there are a ton of technical challenges to this idea. Perhaps this is a good candidate for GSoC?
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org