Yeah, Rob is smart. don't run crap in production. Run what others are stable
at. If you are running the latest greatest dumbest craziest in prod then you
ask for fail, and you will get just that.
FAIL
On Jul 24, 2013, at 12:06 PM, Robert Coli wrote:
> A better solution would likely involve
Last I heard only Oracle's JDK was officially supported with Cassandra,
possibly nitpicky but is this still the case?
On Jun 26, 2012, at 3:37 PM, Dustin Wenz wrote:
> (OpenJDK 7) was pegged at 200% CPU
We have a very hot CF which we use essentially as a durable memory cache for
our application. It is about 70MBytes in size after being fully populated. We
completely overwrite this entire CF every few minutes (not delete). Our hope
was that the CF would stay around 70MB in size, but it grows
Okay I figured this out, the default for MemtableFlushAfterMins is not 60
minutes like some here said and what datastax docs say
(http://www.datastax.com/docs/0.8/configuration/storage_configuration), it's 24
hours (1440). I changed them all to 60 for every CF and now commit logs only
hang aro
> > 86GB in commitlog and 42GB in data
>
> Whoa, that seems really wrong, particularly given your data spans 13 months.
> Have you changed any of the default cassandra.yaml setting? What is the
> maximum memtable_flush_after across all your CFs? Any warnings/errors in the
> Cassandra log?
>
Thanks Dan, good info.
> First off, what version of Cassandra are you using?
Sorry my bad, 0.8.4
> Provided you are using a recent Cassandra version (late 0.7 or 0.8.x) I doubt
> the commit log is your problem. My experience using Cassandra as a time
> series data store (with a full 30 days of
I run a single node cassandra instance, and we have lots of overwrites on a hot
CF and disk utilization seems to grow pretty fast. We've noticed that when we
restart cassandra disk utilization decreases dramatically (dramatic being
something close to 50%). Most of this growth seems to be in th
I'm looking for advice for running cassandra 8.+ on a single node. Would love
to hear stories about how much RAM you succeeded with, etc.
Currently we are running with a 4GB heap size. Hardware is 4 cores and 8GB
physical memory. We're not opposed to going to 16GB of memory or even 32GB.
W
