Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Invalid
-
4.8.1
-
None
-
None
Description
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
Attachments
Issue Links
- is duplicated by
-
SOLR-8146 Allowing SolrJ CloudSolrClient to have preferred replica for query/read
- Resolved
- is part of
-
SOLR-6220 Replica placement strategy for solrcloud
- Closed
- is related to
-
SOLR-6027 Replica assignments should try to take the host name into account so all replicas don't end up on the same host
- Resolved
- relates to
-
SOLR-6273 Cross Data Center Replication
- Resolved