[
https://issues.apache.org/jira/browse/SOLR-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076259#comment-17076259
]
Erick Erickson commented on SOLR-6205:
--------------------------------------
[~noble.paul] [~shalin]
Can we close this? This is already done with Snitches in rule-based replica
placement and, I assume, autoscaling policy...
> Make SolrCloud Data-center, rack or zone aware
> ----------------------------------------------
>
> Key: SOLR-6205
> URL: https://issues.apache.org/jira/browse/SOLR-6205
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.8.1
> Reporter: Arcadius Ahouansou
> Assignee: Noble Paul
> Priority: Major
>
> Use case:
> Let's say we have SolrCloud deployed across 2 Datacenters, racks or zones A
> and B
> There is a need to have a SolrCloud deployment that will make it possible to
> have a working system even if one of the Datacenter/rack/zone A or B is lost.
> - This has been discussed on the mailing list at
> http://lucene.472066.n3.nabble.com/SolrCloud-multiple-data-center-support-td4115097.html
> and there are many workarounds that require adding more moving parts to the
> system.
> - On the above thread, Daniel Collins mentioned
> https://issues.apache.org/jira/browse/ZOOKEEPER-107
> which could help solve this issue.
> - Note that this is a very important feature that is overlooked most of the
> time.
> - Note that this feature is available in ElasticSearch.
> See
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-cluster.html#allocation-awareness
> and
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-cluster.html#forced-awareness
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
