the three time-line column families and load
> the value of the column that is most recent given a cut-off timestamp. The
> value is the row key of the actual event, which we then load as well. We do
> that in batches of 100 rows at a time.
>
> Deletes:
> Every night we del
t in
batches of 100 rows at a time.
Deletes:
Every night we delete all events that are older than 2 days. Again in batches
of 100 rows.
Thanks for helping!
Ralf
From: Alain RODRIGUEZ [arodr...@gmail.com]
Sent: Thursday, May 02, 2013 09:12
To: user@cassandra.apac
Well, maybe should you describe us your hardware and the C* release toi are
using. Also give us some metrics.
Le 30 avr. 2013 18:48, "Steppacher Ralf" <
ralf.steppac...@derivativepartners.com> a écrit :
> Hi,
>
> I have troubles finding some quantitative information as to how a healthy
> Cassandr
Hi,
I have troubles finding some quantitative information as to how a healthy
Cassandra node should look like (CPU usage, number of flushes,SSTables,
compactions, GC), given a certain hardware spec and read/write load. I have
troubles gauging our first and only Cassandra node, whether it needs
