Apache Cassandra
is an
open-source NoSQL data store that is designed primarily to provide a robust
fault tolerant distributed and decentralized data store that is highly durable
and scalable.
The click-to-deploy interface for configuring Apache Cassandra clusters on Google Compute Engine allows you to easily select your configuration options and get up and running in a few minutes. Deploying your Cassandra cluster in this manner is ideal for getting started quickly with development, performance testing, or capacity planning.
By default, the deployment consists of three Cassandra servers with the following configuration:
-
8 core, 32 GB memory (
n1-standrard-8) virtual machine instances. - 1000 GB persistent disk volume attached.
To fit your needs, you can select different machine types , choose a different volume size to fit your storage and performance requirements , and change the number of servers to deploy.
Objectives
- Deploy an Apache Cassandra cluster on Google Compute Engine
- Configure your cluster
Quickly deploy Cassandra on Compute Engine
The Google Developers Console provides a simple interface that you can use to quickly configure your Cassandra cluster.
-
In the Cassandra click-to-deploy page in the Google Developers Console , specify your configuration settings or use the default values.
If you are doing performance testing, choose your data disk size and machine types appropriately.
-
Click Deploy cluster
-
Optional: Install the Cloud SDK to be able to connect to your virtual machine instances when deployment finishes.
The deployment can take a few minutes, when it finishes, you can follow the
provided link to list your virtual machine instances. You can connect to your
instances by using the
gcutil ssh <instance-name>
command to perform further
configuration or to perform other tests such as testing.
When you are finished with the cluster, you can click the Delete Cluster button in the Developers Console to stop all instances and destroy the associated data disks.
Next steps
You might also want to learn about how the Cassandra cluster was deployed. You can learn how Deployment Manager was used and extend that knowledge to your own projects.
Next: Learn how Cassandra was deployed
Troubleshooting
If a deployment fails to complete successfully, check the error message in the Developers Console. If the problem is a CPU quota issue or other problem that you can correct, delete the deployment, correct the problem, and try again.
If the error message on the Developers Console does not provide
sufficient detail about the failure, check the Deployment Manager output on
the virtual machine instances that were launched. On each instance, there will
be a directory
/gagent/metaOutput
with a set of numbered files:
stdoutN.txt
,
stderrN.txt
,
exitcodeN.txt
. Each set of such files corresponds to the
sequenced command that was executed by Deployment Manager for your deployment
on that instance.
To get a list of your compute engine instances, check the Compute Engine list of virtual machine instances in the Developers Console or run the following command:
$ gcloud compute instances list -l
To ssh to an instance:
$ gcloud compute ssh <instance> --zone=<zone>
If you have problems that you cannot resolve or have questions head to Stack Overflow .