Running Cassandra in Containers. Github example

1 view
Skip to first unread message

Lakhinder Walia

unread,
Dec 18, 2015, 1:05:19 AM12/18/15
to google-c...@googlegroups.com
Hi, this is regarding the example off the following URL:


I just upgraded to the latest code today, commit: 08c2cba266ba5205a8c5341279ded49776f64cee, and ran the example. Platform Ubuntu 14.04 master. Ubuntu 15.04 minion.

The Cassandra docker containers never came up successfully. In fact they don't show up in the 'docker ps' command on Minion,: except the 'pause' part. 

Here is the result from the master:

/usr/src/kubernetes/cluster# ./kubectl.sh get po
NAME              READY     STATUS         RESTARTS   AGE
cassandra         0/1       ExitCode:126   4          2m
cassandra-0en4h   0/1       ExitCode:126   4          2m
cassandra-btog7   0/1       ExitCode:126   4          2m
cassandra-gemwx   0/1       ExitCode:126   4          2m

And the pods restarted continuously ..

(My previous code, a few days older, didn't have this issue).

=================================================

Just to do a sanity check: I created nginx pods, and they came up fine

./kubectl.sh run my-nginx --image=nginx --replicas=2 --port=80

/usr/src/kubernetes/cluster# ./kubectl.sh get po
NAME             READY     STATUS    RESTARTS   AGE
my-nginx-1jduj   1/1       Running   0          24s
my-nginx-wp310   1/1       Running   0          24s

Lakhinder Walia

unread,
Dec 18, 2015, 1:07:21 AM12/18/15
to google-c...@googlegroups.com
One more thing to add: I had to add the --validate=false option when creating the cassandra-service. The example doesn't mention it.

Lakhinder Walia

unread,
Dec 19, 2015, 10:51:52 PM12/19/15
to google-c...@googlegroups.com
More information: I just picked up (randomly) an older version of the code (commit 3136acad8b0adef118a961b3e63515f49cca2257), and the commands above were repeated. And Cassandra ran without any restarts.

May I dare to suggest it is either the new kubernetes code, or maybe some deficiency in my setup/testing that it is not compatible with new code!?

My setup: One master node. One minion. Both ubuntu.

Docker version 1.9.1, build a34a1d5
etcd version 2.2.2
flannel version v0.5.3-67-g0a74bc0
go version go1.5.1 linux/amd64

Jay Vyas

unread,
Dec 20, 2015, 10:44:04 AM12/20/15
to google-c...@googlegroups.com

Three quick checks:

- docker ps -a should show something?  
- Also, what about kubectl describe cassandra-0en4h?
- Is your network overlay working? (journactl -f -u flanneld).

Now, if nothing turns up there,

-  i would suggest running the e2e test for something like networking.go or k8petstore.go on a fresh cluster. That should confirm that your  cluster is working including the network overlay for round trip communication over service end points.
For directions on running the e2es using ginkgo, see the docs/ getting started with e2e tests.

And finally If it's still broke, then Let's create an issue for this in github and we will take a look and get Cassandra back up and running :). Thanks!

On Dec 18, 2015, at 1:05 AM, Lakhinder Walia <lakhind...@maginatics.com> wrote:

Hi, this is regarding the example off the following URL:


I just upgraded to the latest code today, commit: 08c2cba266ba5205a8c5341279ded49776f64cee, and ran the example. Platform Ubuntu 14.04 master. Ubuntu 15.04 minion.

The Cassandra docker containers never came up successfully. In fact they don't show up in the 'docker ps' command on Minion,: except the 'pause' part. 

Here is the result from the master:

/usr/src/kubernetes/cluster# ./kubectl.sh get po
NAME              READY     STATUS         RESTARTS   AGE
cassandra         0/1       ExitCode:126   4          2m   0/1       ExitCode:126   4          2m
cassandra-btog7   0/1       ExitCode:126   4          2m
cassandra-gemwx   0/1       ExitCode:126   4          2m

And the pods restarted continuously ..

(My previous code, a few days older, didn't have this issue).

=================================================

Just to do a sanity check: I created nginx pods, and they came up fine

./kubectl.sh run my-nginx --image=nginx --replicas=2 --port=80

/usr/src/kubernetes/cluster# ./kubectl.sh get po
NAME             READY     STATUS    RESTARTS   AGE
my-nginx-1jduj   1/1       Running   0          24s
my-nginx-wp310   1/1       Running   0          24s

--
You received this message because you are subscribed to the Google Groups "Containers at Google" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-contain...@googlegroups.com.
To post to this group, send email to google-c...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-containers.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages