in the sstable have been flushed.
> But commitlog_total_space_in_mb is the correct way to control that.
>
> Hope that helps.
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 27/02/2012, at 4:48 PM, Xaero S wrot
The challenge that we face is that our commitlog disk capacity is much much
less (under 10 GB in some cases) than the disk capacity of SSTables. So we
cannot really have the commitlog data continuously growing. This is the
reason that we need to be able to tune the the way we flush the memtables.
>
I recently started using Cassandra 1.0.4 and observed that it takes a lot
longer to flush the commit logs to SSTables, than was observed in versions
0.7.X and 0.8.X under constant load conditions with commitlog_sync as
periodic and commitlog_sync_period_in_ms as 1. As more data gets
retained in
I have been trying to figure out how to secure/encrypt the traffic between
the client (Hector) and the Cassandra Server. I looked at this link
https://issues.apache.org/jira/browse/THRIFT-106 But since thrift sits on a
layer after Hector, i am wondering how i can get Hector to use the right
Thrift
Can someone point me to a document that explains how to interpret
CFHistograms output? i went through
http://narendrasharma.blogspot.com/2011/04/cassandra-07x-understanding-output-of.htmlwhich
is a good beginning, but was wondering if there was anything more
detailed. For e.g when i run CFHistogram
Hi,
You just need to use the update column family command on the cassandra-cli
and specify the columns and their metadata. To get the metadata of the
columns in the CF, you can do describe keyspace . Keep in mind
that, in your update CF command, the other columns that must continue to
have the sec
