I should add - there is probably an option (c) of fiddling with a bunch of
tuning parameters to try to nurse things through with your current config
but I’m not sure that’s useful unless you really need to make the current
set up work for some reason.
On Sun, 12 Jun 2016 at 15:23 Ben Slater
Hi Tobin,
4G RAM is a pretty small machine to be using to run Cassandra. As I
mentioned, 8G of heap is the normal recommendation for a production machine
which means you need at least 14-16G total (and can get performance benefit
from more).
I agree disk space doesn’t look to really be an issue
related to https://issues.apache.org/jira/browse/CASSANDRA-11330, most of
the system tables will work but batches are kinda special cased and uses
the localpartitioner (see:
I have been trying to obtain json dump of batches table using sstabledump
but I get this exception:
$ sstabledump
/sstable/data/system/batches-919a4bc57a333573b03e13fc3f68b465/ma-277-big-Data.db
Exception in thread "main"
org.apache.cassandra.exceptions.ConfigurationException: Cannot use abstract
Hi Ben,
I think the degraded mode is caused by one or both of these...
• WARN [main] 2016-06-10 14:23:01,690 StartupChecks.java:118 -
jemalloc shared library could not be preloaded to speed up memory allocations
• WARN [main] 2016-06-10 14:23:01,691 StartupChecks.java:150 - JMX
