Use zone redundant Managed Instance for Apache Cassandra clusters#
Reliability · Managed Instance for Apache Cassandra · Rule · 2025_12 · Important
Use zone redundant Managed Instance for Apache Cassandra clusters in supported regions to improve reliability.
Description#
Managed Instance for Apache Cassandra supports zone redundancy through availability zones. When availability zones are enabled, nodes are physically separated across multiple zones within an Azure region.
Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking infrastructure. This physical separation ensures that if one zone experiences an outage, your Cassandra cluster continues to serve read and write requests from nodes in other zones without downtime.
With zone redundancy enabled, Managed Instance for Apache Cassandra provides:
- Automatic distribution of nodes across zones.
- Continuous availability during zonal failures.
- Enhanced durability by maintaining multiple replicas across separate physical locations.
- Protection against datacenter-level disasters while maintaining low-latency access.
Zone redundancy must be configured when you create a data center by setting availabilityZone to true.
This setting cannot be changed after the datacenter is created.
Zone redundancy is only available in regions that support availability zones.
Recommendation#
Consider enabling availability zones for data center clusters that support them to improve workload resiliency.
Examples#
Configure with Azure template#
To deploy clusters that pass this rule:
- Set
properties.availabilityZonetotrue.
For example:
{
"type": "Microsoft.DocumentDB/cassandraClusters/dataCenters",
"apiVersion": "2024-11-15",
"name": "[format('{0}/{1}', parameters('clusterName'), parameters('dataCenterName'))]",
"location": "[parameters('location')]",
"properties": {
"dataCenterLocation": "[parameters('location')]",
"delegatedSubnetId": "[parameters('delegatedSubnetId')]",
"nodeCount": 3,
"sku": "Standard_E8s_v5",
"diskCapacity": 4,
"availabilityZone": true
}
}
Configure with Bicep#
To deploy clusters that pass this rule:
- Set
properties.availabilityZonetotrue.
For example:
resource dataCenter 'Microsoft.DocumentDB/cassandraClusters/dataCenters@2024-11-15' = {
parent: cluster
name: datacenterName
location: location
properties: {
dataCenterLocation: location
delegatedSubnetId: delegatedSubnetId
nodeCount: 3
sku: 'Standard_E8s_v5'
diskCapacity: 4
availabilityZone: true
}
}
Notes#
This rule only applies to Managed Instance for Apache Cassandra deployment model.
Links#
- RE:05 Redundancy
- Azure regions with availability zone support
- Reliability: Level 1
- Architecture strategies for using availability zones and regions
- Best practices for high availability and disaster recovery
- Azure deployment reference