Apache Cassandra is a free and open-source distributed database management system designed to handle large amounts of data across many commodity servers, providing high availability with no single point of failure. Cassandra offers robust support for clusters spanning multiple datacenters, with asynchronous masterless replication allowing low latency operations for all clients.
docker run --name cassandra bitnami/cassandra:latestcassandra:
image: bitnami/cassandra:latest
The recommended way to get the Bitnami Cassandra Docker Image is to pull the prebuilt image from the Docker Hub Registry.
docker pull bitnami/cassandra:latestTo use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
docker pull bitnami/cassandra:[TAG]If you wish, you can also build the image yourself.
docker build -t bitnami/cassandra:latest https://github.com/bitnami/bitnami-docker-cassandra.gitIf you remove every container and volume all your data will be lost, and the next time you run the image the application will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed. If you are using docker-compose your data will be persistent as long as you don't remove application_data data volumes. If you have run the containers manually or you want to mount the folders with persistent data in your host follow the next steps:
Note! If you have already started using your application, follow the steps on backing up to pull the data from your running container down to your host.
The image exposes a volume at /bitnami/cassandra for the Cassandra data and configurations. For persistence you can mount a directory at this location from your host. If the mounted directory is empty, it will be initialized on the first run.
docker run -v /path/to/cassandra-persistence:/bitnami/cassandra bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/cassandra-persistence:/bitnami/cassandra
If you want to connect to your Cassandra server inside another container, you can use the linking system provided by Docker.
The first step is to start our Cassandra server.
Docker's linking system uses container ids or names to reference containers. We can explicitly specify a name for our Cassandra server to make it easier to connect to other containers.
docker run --name cassandra bitnami/cassandra:latestNow that we have our Cassandra server running, we can create another container that links to it by
giving Docker the --link option. This option takes the id or name of the container we want to link
it to as well as a hostname to use inside the container, separated by a colon. For example, to have
our Cassandra server accessible in another container with server as it's hostname we would pass
--link cassandra:server to the Docker run command.
The Bitnami Cassandra Docker Image also ships with a Cassandra client, but by default it will start a server. To start the client instead, we can override the default command Docker runs by stating a different command to run after the image name.
docker run --rm -it --link cassandra:server bitnami/cassandra cqlsh serverWe started the Cassandra client passing in the -h option that allows us to specify the hostname of the
server, which we set to the hostname we created in the link.
Note! You can also run the Cassandra client in the same container the server is running in using the Docker exec command.
docker exec -it cassandra-server cqlshCopy the snippet below into your docker-compose.yml to add Cassandra to your application.
cassandra:
image: bitnami/cassandra:latest
Update the definitions for containers you want to access your Cassandra server from to include a link to the cassandra entry you added in Step 1.
myapp:
image: myapp
links:
- cassandra:cassandra
Inside myapp, use cassandra as the hostname for the Cassandra server.
When you start the cassandra image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:
- For docker-compose add the variable name and value under the application section:
application:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_TRANSPORT_PORT=7000- For manual execution add a
-eoption with each variable and value:
$ docker run -d -e CASSANDRA_PORT=7000 -p 7000:7000 --name cassandra -v /your/local/path/bitnami/cassandra:/bitnami/cassandra --network=cassandra_network bitnami/cassandra
Available variables:
CASSANDRA_TRANSPORT_PORT: Inter-node cluster communication port. Default: 7000CASSANDRA_SSL_TRANSPORT_PORT: SSL inter-node cluster communication port. Default: 7001CASSANDRA_JMX_PORT: JMX connections port. Default: 7199CASSANDRA_CQL_PORT: Client port. Default: 9042.CASSANDRA_RPC_PORT: Thrift RPC service connection port. Default: 9160CASSANDRA_USER: Cassandra user name. Defaults: cassandraCASSANDRA_PASSWORD: Cassandra user password. Default: cassandraCASSANDRA_HOST: Hostname used to configure Cassandra. It can be either an IP or a domain. If left empty, it will be resolved to the machine IP.CASSANDRA_CLUSTER_NAME: Cluster name to configure Cassandra.. Defaults: My ClusterCASSANDRA_SEEDS: Hosts that will act as Cassandra seeds. No defaults.CASSANDRA_ENDPOINT_SNITCH: Snitch name (which determines which data centers and racks nodes belong to). Default SimpleSnitch
Passing the CASSANDRA_PASSWORD environment variable when running the image for the first time will set the Cassandra server password to the value of CASSANDRA_PASSWORD.
docker run --name cassandra -e CASSANDRA_PASSWORD=password123 bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_PASSWORD=password123
A cluster can easily be setup with the Bitnami Cassandra Docker Image using the following environment variables
CASSANDRA_HOST: Hostname used to configure Cassandra. It can be either an IP or a domain. If left empty, it will be resolved to the machine IP.CASSANDRA_CLUSTER_NAME: Cluster name to configure Cassandra.. Defaults: My ClusterCASSANDRA_SEEDS: Hosts that will act as Cassandra seeds. No defaults.CASSANDRA_ENDPOINT_SNITCH: Snitch name (which determines which data centers and racks nodes belong to). Default SimpleSnitch
docker network create cassandra_networkdocker run --name cassandra-node1 \
--net=cassandra_network \
-p 9042:9042 \
-e CASSANDRA_CLUSTER_NAME=cassandra-cluster \
-e CASSANDRA_SEEDS=cassandra-node1,cassandra-node2 \
bitnami/cassandra:latestIn the above command the container is added to a cluster named cassandra-cluster using the CASSANDRA_CLUSTER_NAME. The CASSANDRA_CLUSTER_HOSTS parameter set the name of the nodes that set the cluster so we will need to launch other container for the second node. Finally the CASSANDRA_NODE_NAME parameter allows to indicate a known name for the node, otherwise cassandra will generate a randon one.
docker run --name cassandra-node2 \
--net=cassandra_network \
-e CASSANDRA_CLUSTER_NAME=cassandra-cluster \
-e CASSANDRA_SEEDS=cassandra-node1,cassandra-node2 \
bitnami/cassandra:latestIn the above command a new cassandra node is being added to the cassandra cluster indicated by CASSANDRA_CLUSTER_NAME.
You now have a two node Cassandra cluster up and running which can be scaled by adding/removing nodes.
With Docker Compose the cluster configuration can be setup using:
version: '2'
services:
cassandra-node1:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_CLUSTER_NAME=cassandra-cluster
- CASSANDRA_SEEDS=cassandra-node1,cassandra-node2
cassandra-node2:
image: bitnami/cassandra:latest
environment:
- CASSANDRA_CLUSTER_NAME=cassandra-cluster
- CASSANDRA_SEEDS=cassandra-node1,cassandra-node2The image looks for configuration in the conf/ directory of /bitnami/cassandra. As as mentioned in Persisting your application you can mount a volume at this location and copy your own configurations in the conf/ directory. The default configuration will be copied to the conf/ directory if it's empty.
Run the Cassandra image, mounting a directory from your host.
docker run --name cassandra -v /path/to/cassandra-persistence:/bitnami/cassandra bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/cassandra-persistence:/bitnami/cassandra
Edit the configuration on your host using your favorite editor.
vi /path/to/cassandra-persistence/conf/cassandra.yamlAfter changing the configuration, restart your Cassandra container for changes to take effect.
docker restart cassandraor using Docker Compose:
docker-compose restart cassandraFurther Reading:
The Bitnami Cassandra Docker image sends the container logs to the stdout. To view the logs:
docker logs cassandraor using Docker Compose:
docker-compose logs cassandraYou can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.
To backup your data, configuration and logs, follow these simple steps:
docker stop cassandraor using Docker Compose:
docker-compose stop cassandraWe need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
docker run --rm -v /path/to/cassandra-backups:/backups --volumes-from cassandra busybox \
cp -a /bitnami/cassandra:latest /backups/latestor using Docker Compose:
docker run --rm -v /path/to/cassandra-backups:/backups --volumes-from `docker-compose ps -q cassandra` busybox \
cp -a /bitnami/cassandra:latest /backups/latestRestoring a backup is as simple as mounting the backup as volumes in the container.
docker run -v /path/to/cassandra-backups/latest:/bitnami/cassandra bitnami/cassandra:latestor using Docker Compose:
cassandra:
image: bitnami/cassandra:latest
volumes:
- /path/to/cassandra-backups/latest:/bitnami/cassandra
Bitnami provides up-to-date versions of Cassandra, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
docker pull bitnami/cassandra:latestor if you're using Docker Compose, update the value of the image property to
bitnami/cassandra:latest.
Before continuing, you should backup your container's data, configuration and logs.
Follow the steps on creating a backup.
docker rm -v cassandraor using Docker Compose:
docker-compose rm -v cassandraRe-create your container from the new image, restoring your backup if necessary.
docker run --name cassandra bitnami/cassandra:latestor using Docker Compose:
docker-compose start cassandraWe'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (
docker version) - Output of
docker info - Version of this container (
echo $BITNAMI_APP_VERSIONinside the container) - The command you used to run the container, and any relevant output you saw (masking any sensitive information)
Copyright (c) 2016 Bitnami
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.