| title | description | author | ms.author | ms.service | ms.topic | ms.date | ms.custom |
|---|---|---|---|---|---|---|---|
Frequently asked questions about Azure Managed Instance for Apache Cassandra from the Azure portal |
Frequently asked questions about Azure Managed Instance for Apache Cassandra. This article addresses questions on when to use managed instances, benefits, throughput limits, supported regions, and other configuration details. |
TheovanKraay |
thvankra |
managed-instance-apache-cassandra |
quickstart |
11/02/2021 |
ignite-fall-2021, mode-ui, ignite-2022 |
This article addresses frequently asked questions about Azure Managed Instance for Apache Cassandra. You'll learn when to use managed instances, their benefits, throughput limits, supported regions, and their configuration details.
The Apache Cassandra database is the right choice when you need scalability and high availability without compromising performance. It's a great platform for mission-critical data due to the linear scalability and proven fault-tolerance on commodity hardware or cloud infrastructure. Azure Managed Instance for Apache Cassandra is a service to manage instances of open-source Apache Cassandra datacenters deployed in Azure.
It can be used either entirely in the cloud or as a part of a hybrid cloud and on-premises cluster. This service is a great choice when you want fine-grained configuration and control you have in open-source Apache Cassandra, without any maintenance overhead.
Azure Managed Instance for Apache Cassandra is delivered by the Azure Cosmos DB team. It's a standalone managed service for deploying, maintaining, and scaling open-source Apache Cassandra data-centers and clusters. Azure Cosmos DB for Apache Cassandra on the other hand is a Platform-as-a-Service, providing an interoperability layer for the Apache Cassandra wire protocol. If your expectation is for the platform to behave in exactly the same way as any Apache Cassandra cluster, you should choose the managed instance service. To learn more, see Differences between Azure Managed Instance for Apache Cassandra and Azure Cosmos DB for Apache Cassandra.
No, there's no architectural dependency between Azure Managed Instance for Apache Cassandra and the Azure Cosmos DB backend.
The service currently supports Cassandra versions 3.11 and 4.0. By default, version 3.11 is deployed, as version 4.0 is currently in public preview. See our Azure CLI Quickstart (step 5) for specifying Cassandra version during cluster deployment.
Yes, the SLA is published here.
Currently the managed instance is available in a limited number of regions.
These limits depend on the Virtual Machine SKUs you choose.
We use cassandra-reaper.io. It's set up to run automatically for you.
The managed instance charges are based on the underlying VM cost, with a small markup. For more information, see the pricing page.
Yes, you can embed YAML file configurations as part of an Azure Resource Manager template deployment.
The Prometheus server is hosted to monitor activity across your cluster, and it exposes an endpoint. This maintains 10 minutes or 10 GB of data (whichever threshold is reaches first). To use this monitoring, you need to set up a federation and an appropriate dashboard tool such as Grafana.
Yes, it provides full backups to Azure Storage and restores to a new cluster. For more information, see here.
How can I migrate data from my existing Apache Cassandra cluster to Azure Managed Instance for Apache Cassandra?
Azure Managed Instance for Apache Cassandra supports all of the features in Apache Cassandra to replicate and stream data between data-centers.
Can I pair an on-premises Apache Cassandra cluster with the Azure Managed Instance for Apache Cassandra?
Yes, you can configure a hybrid cluster with Azure Virtual Network injected data-centers deployed by the service. Managed Instance data-centers can communicate with on-premises data-centers within the same cluster ring.
Provide feedback via user voice feedback using the category "Managed Apache Cassandra".
To fix an issue with your account, file a support request in the Azure portal.
All the read-only nodetool commands such as status are available through Azure CLI. However, operations such as node addition aren't available, because we manage the health of nodes in the managed instance. In the Hybrid mode, you can connect to the cluster with nodetool. However, using nodetool isn't recommended, as it could destabilize the cluster. It may also invalidate any production support SLA relating to the health of the managed instance datacenters in the cluster.
The settings for table metadata such as bloom filter, caching, read repair chance, gc_grace, and compression memtable_flush_period are fully supported as with any self-hosted Apache Cassandra environment.
Yes. You can find a sample for deploying a cluster with a datacenter here.
To learn about frequently asked questions in other APIs, see: