I saw a thread from April 2016 talking about Cassandra and Kubernetes, and
have a few follow up questions.  It seems that especially after v1.2 of
Kubernetes, and the upcoming 1.3 features, this would be a very viable
option of running Cassandra on.

My questions pertain to HostIds and Scaling Up/Down, and are related:

1.  If a container's host dies and is then brought up on another host, can
you start up with the same PersistentVolume as the original container had?
Which begs the question would the new container get a new HostId, implying
it would need to bootstrap into the environment?   If it's a bootstrap,
does the old one get deco'd/assassinated?

2. Scaling up/down.  Scaling up would be relatively easy, as it should just
kick off Bootstrapping the node into the cluster, but what if you need to
scale down?  Would the Container get deco'd by the scaling down process? or
just terminated, leaving you with potential missing replicas

3. Scaling up and increasing the RF of a particular keyspace, would there
be a clean way to do this with the kubernetes tooling?

In the end I'm wondering how much of the Kubernetes + Cassandra involves
nodetool, and how much is just a Docker image where you need to manage that
all yourself (painfully)

-- 
--mike

Reply via email to