This happened to me again. I checked via dmesg and it looks like the OOM killer kicked in. I wonder if that is the same in your case? Looking at the currently defined memory, I see it's set to 512MB. Any reason we can't double that to 1GB? I think that's pretty reasonable for most users and the VM can always be suspended when not in use.
-- Michael Mior [email protected] 2016-02-23 13:50 GMT-05:00 Julian Hyde <[email protected]>: > I'm using the latest https://github.com/vlsi/calcite-test-dataset. It > seems that Cassandra runs for a day or so (I can run Calcite's full > suite, including integration tests), then Cassandra dies (the 4 > CassandraAdapterIT tests fail). When I log into the VM, Cassandra is > not available: > > $ calcite-test-dataset/vm/ > $ vagrant ssh > Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-30-generic x86_64) > > * Documentation: https://help.ubuntu.com/ > Last login: Fri Feb 19 12:33:59 2016 from 10.0.2.2 > vagrant$ cqlsh -k twissandra `hostname -I` > Connection error: ('Unable to connect to any servers', {'10.0.2.15': > error(111, "Tried connecting to [('10.0.2.15', 9042)]. Last error: > Connection refused")}) > > Restarting the service doesn't help: > > vagrant$ sudo service cassandra restart > * Restarting Cassandra cassandra > [OK] > start-stop-daemon: warning: failed to kill 11109: No such process > vagrant$ sudo service cassandra restart > * Restarting Cassandra cassandra > [ OK ] > vagrant$ cqlsh -k twissandra `hostname -I` > Connection error: ('Unable to connect to any servers', {'10.0.2.15': > error(111, "Tried connecting to [('10.0.2.15', 9042)]. Last error: > Connection refused")}) > > Restarting the VM solves the problem. > > Is anyone else seeing this? Any ideas how to fix Cassandra so that it > stays up? > > Julian >
