calvinlfer/compose-cassandra-cluster

README.md A docker-compose blueprint that describes a 3 node Cassandra cluster.It only exposes important Cassandra ports on the seed node to the hostmachine. Internally, all of the nodes will be a part of the same Dockernetwork and will form a cluster using that Docker network.InstructionsIn order to bring up the cluster:Use docker-compose up to see the logs of all the containersUse docker-compose up -d if you want it to run in the foregroundIn order to clean up the cluster, use docker-compose downNotesYou need to make sure that the Docker daemon has enough of resourcesotherwise you will encounter exit code 137 (Out of Memory Killer) onyour containers.When you create a single node cluster and you try to add more nodes tothe cluster, you must add them one by one. This means that you cannothave multiple nodes join the cluster (by pointing to the seed node) atthe same time. You must add a cluster, wait for it to join the ring andstabilize before you can begin to add another cluster. This is why youwill see an additional delay on start up between the non-seed nodes.If you attempt to join a new node whilst stabilization has not yet beenachieved, you will see an error like this:ERROR [main] 2017-08-22 23:19:11,055 CassandraDaemon.java:706 - Exception encountered during startupjava.lang.UnsupportedOperationException: Other bootstrapping/leaving/moving nodes detected, cannot bootstrap while cassandra.consistent.rangemovement is trueThis articlediscusses the implications of turning cassandra.consistent.rangemovementoff.CreditsThe Last Pickle