Skip to content


Subversion checkout URL

You can clone with
Download ZIP
A script to easily create and destroy an Apache Cassandra cluster on localhost

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.


CCM (for Cassandra Cluster Manager ... or something)

A script/library to create, launch and remove a Apache Cassandra cluster on

The goal of ccm and ccmlib is to make is easy to create, manage and destroy a
small cluster on a local box. It is meant for testing of a Cassandra cluster.


- A working python installation (tested to work with python 2.7).
- pyYAML ( -- 'sudo easy_install pyYaml')
- ccm works on localhost only for now. So if you want to create more than one
  node clusters the simplest way is to use multiple loopback aliases. On
  modern linux distribution you will probably have nothing to do, but
  on mac os x, you would have to create such aliases with
    sudo ifconfig lo0 alias up
    sudo ifconfig lo0 alias up
  Note that the usage section assumes that at least, and are available.
- I'm pretty sure this doesn't work under Windows, but I accept pull requests


ccm uses python distutils so from the source directory:
sudo ./ install


Let's say you want to fire up a 3 nodes Cassandra cluster.

* Short version *

ccm create test -v 0.8.6
ccm populate -n 3
ccm start

* Longer version *

ccm works from a Cassandra source tree (not the jars). There is two way to
tell ccm how to find the sources:
  1. if you have downloaded *and* compiled Cassandra sources, you can ask ccm
     to use that by initiating a new cluster with:
        ccm create test --cassandra-dir=<path/to/cassandra-sources>
     or, from that source tree directory, simply
        ccm create test
  2. you can ask ccm to use a released version of Cassandra. For instance to
     use Cassandra 0.8.6, do
        ccm create test -v 0.8.6
     When doing so, ccm will download the source (from,
     compile them and set the new cluster to use those. This means in
     particular that this command can take a few minutes the first time you
     create a cluster for a given version. After the first time, ccm keeps the
     sources compile in ~/.ccm/repository/, so the same command will be fast
     the next times (note however that if you create cluster with a lot of
     different versions, this will take you disk space).

Once the cluster is created, you can populate it (with 3 nodes) and start all
the nodes with:
  ccm populate -n 3
  ccm start

That will start 3 nodes on IP 127.0.0.[1, 2, 3] on port 9160 for thrift, port
7000 for the internal cluster communication and ports 7100, 7200 and 7300 for JMX.
You can check that the cluster is correctly set up with
  ccm node1 ring

You can then boostrap a 4th node with
  ccm add node4 -i -j 7400 -b
(populate is just a shortcut for adding multiple nodes initially)

ccm then provides a number of conveniences, like flushing all of the nodes of
the cluster:
  ccm flush
or only one node:
  ccm node2 flush

You can also easily look at the log file of a given node with:
  ccm node1 showlog

Finally, you can get rid of the whole cluster (which will stop the node and
remove all the data) with
  ccm remove

The list of other provided command is available through
then each command is then documented through the -h (or --help) flag. For
instance 'ccm add -h' describe the options for 'ccm add'.

Where are things stored

By default, ccm stores all the node data and configuration files under ~/.ccm/cluster_name/.
This can be overridden using the --config-dir option with each command.


The ccm facilities are available programmatically through ccmlib. This could
be use to implement automated tests again Cassandra. An hopefully self
explanatory simple example of use of ccmlib could be:

  import ccmlib

  cluster = ccmlib.Cluster(CLUSTER_PATH, 'test', cassandra_version='0.8.6')
  [node1, node2, node3] = cluster.nodelist()

  # do some test on the cluster/nodes. To connect to a node through thrift,
  # the host and port to a node is available through
  #   node.network_interfaces['thrift']


  # do some other test

  # after the test, you can leave the cluster running, you can stop all nodes
  # using cluster.stop() but keep the data around (in CLUSTER_PATH/test), or
  # you can remove everything with cluster.remove()

Sylvain Lebresne <>
Something went wrong with that request. Please try again.