Skip to content
This repository has been archived by the owner on Dec 20, 2024. It is now read-only.

Multi Data Center Deployments

Jump to bottom
JoeWinter edited this page Sep 25, 2014 · 3 revisions

[Table of Contents](https://github.com/dell-oss/Doradus/wiki/Doradus Administration: Table-of-Contents) | [Previous](https://github.com/dell-oss/Doradus/wiki/Expanding the Cluster) | [Next](https://github.com/dell-oss/Doradus/wiki/Hardware Recommendations)
Deployment Guidelines: Multi Data Center Deployments

Larger deployment topologies are also possible. Cassandra clusters can scale to hundreds of nodes. Each Cassandra node can also be configured with a specific rack and data center assignment. A rack is usually network-near to other racks in the same data center but independently powered. Data centers are geographically dispersed. With rack and data center awareness, Cassandra can use a replication policy that ensures maximum availability should a node, rack, or entire data center fail. An example of a multi-rack/multi-data center deployment is shown below:

Figure 7 – Multi-Data Center Deployment

Advanced configurations such as these are beyond the scope of this document, but information about Cassandra configuration is publicly available.

Technical Documentation

[Doradus OLAP Databases](https://github.com/dell-oss/Doradus/wiki/Doradus OLAP Databases)

Doradus Spider Databases

Doradus Administration

Clone this wiki locally