Re: Why compacting process uses more data that is expected

Indeed, nodetool compactionstats shows uncompressed sizes. As Oleksandr suggests, use the table compression ratio to compute the actual size on disk. It would actually be a great improvement for ops if we could add a switch to compactionstats in order to have the compression ratio applied automati

Re: Why compacting process uses more data that is expected

On Jan 4, 2017 17:58, "Jean Carlo" wrote: Hello guys I have a table with 34Gb of data in sstables (including tmp). And I can see cassandra is doing some compactions on it. What surprissed me is that nodetool compactionstats says he is compacting 138.66GB root@node001 /root # nodetool compacti

Re: Cipher Suite Cassandra 2.1.14 Encryption

Is AES-GCM supported in python by default? I have a vague recollection that it is not (certainly possible my knowledge is outdated as well). On Wed, Dec 21, 2016 at 10:21 AM, Jacob Shadix wrote: > I was testing client encryption w/cqlsh and get the following error when > using TLS_DHE_RSA_WITH_A

Odd behavior when querying using two SASI indexes

Seeing queries return 0 rows incorrectly, running 3.9 Setup: create table test1(id1 text PRIMARY KEY, val1 text, val2 text); create custom index test1_idx_val1 on test1(val1) using 'org.apache.cassandra.index.sasi.SASIIndex'; create custom index test1_idx_val2 on test1(val2) using 'org.apache.ca

Is Repair complete?

Can anyone give a better answer to the question "How do I know if a "nodetool repair" is finished?" on http://stackoverflow.com/questions/25064717/how-do-i-know-if-nodetool-repair-is-finished I am trying to prepare to upgrade to DSE 5. I am migrating to incremental repairs first. So I disabled

Re: weird jvm metrics

The metric-reporter is actually leveraged from another project. https://github.com/addthis/metrics-reporter-config Check the version of metric-reporter (in cassandra/lib) and see if it has changed from your old version to your new version. On Wed, Jan 4, 2017 at 12:02 PM, Mike Torra wrote:

Re: Why compacting process uses more data that is expected

What's the total size of your sstables on disk? ls -lah /path/to/table/data On Wed, Jan 4, 2017 at 8:58 AM Jean Carlo wrote: > Hello guys > > I have a table with 34Gb of data in sstables (including tmp). And I can > see cassandra is doing some compactions on it. What surprissed me is that > node

Re: weird jvm metrics

Just bumping - has anyone seen this before? http://stackoverflow.com/questions/41446352/cassandra-3-9-jvm-metrics-have-bad-name From: Mike Torra mailto:mto...@demandware.com>> Reply-To: "user@cassandra.apache.org" mailto:user@cassandra.apache.org>> Date: Wednesd

Why compacting process uses more data that is expected

Hello guys I have a table with 34Gb of data in sstables (including tmp). And I can see cassandra is doing some compactions on it. What surprissed me is that nodetool compactionstats says he is compacting 138.66GB root@node001 /root # nodetool compactionstats -H pending tasks: 103 * compaction

RE: Cassandra CPU perfomance

Hi, A hint : depending on your data set size + your request rate per second, 8 GB of RAM may be too low. And then, CPU might be high due to too frequent GC. More RAM may bring: · More space for OS FS to cache the SSTable files in memory. · A greater heap size, and then, less fr

Re: Reaper repair seems to "hang"

Actually, the problem is related to CASSANDRA-11430 . Before 2.2.6, the notification service did not work with newly deprecated repair methods, on which Reaper still currently relies. C* 2.2.6 and onwards are not affected by this problem and w

Cassandra CPU perfomance

Hi, I deployed a Cassandra 2.2 ring composed by 4 nodes in the cloud with 8 vCPU and 8GB of ram. I am running some tests now with cassandra-stress and YCSB tools to test its performance. I am mainly interested in read requests with a small amount of write requests (95%/5%). Running the experiment