Hi Raman and Chandana.
'unsubscribe cassandra' in google search (probably not the best keywords):
Result 1: http://www.planetcassandra.org/apache-cassandra-mailing-lists/
Result 2: http://mail-archives.apache.org/mod_mbox/cassandra-user/
Result 3: http://cassandra.apache.org/
I did the work for
After a few days I've also tried disabling Linux kernel huge pages
defragement (echo never > /sys/kernel/mm/transparent_hugepage/defrag) and
turning coalescing off (otc_coalescing_strategy: DISABLED), but either did
do any good. I'm using LCS, there are no big GC pauses, and I have set
"concurrent_
I would say only repairing when there is a known problem has a couple of
logical issues off the top of my head:
1. you're assuming hints are successfully delivering within their time window.
There isn't really any indication that I've ever found myself.
2. unless you're using CL ALL you really h
Hi Garo,
Are you using XFS or Ext4 for data? XFS is much better at deleting
large files, such as may happen after a compaction. If you have 26 TB
in just two tables, I bet you have some massive sstables which may
take a while for Ext4 to delete, which may be causing the stalls. The
underlying bloc
You aren't using counters by chance?
regards,
Ryan Svihla
On Jul 22, 2016, 2:00 PM -0500, Mark Rose , wrote:
> Hi Garo,
>
> Are you using XFS or Ext4 for data? XFS is much better at deleting
> large files, such as may happen after a compaction. If you have 26 TB
> in just two tables, I bet you h
Unsubscribe me.
Thank you
From: Ryan Svihla [mailto:r...@foundev.pro]
Sent: viernes, 22 de julio de 2016 14:39
To: user@cassandra.apache.org
Subject: Re: My cluster shows high system load without any apparent reason
You aren't using counters by chance?
regards,
Ryan Svihla
On Jul 22, 2016, 2:
>
> Are you using XFS or Ext4 for data?
We are using XFS. Many nodes have a couple large SSTables (in order of
20-50 GiB), but I havent cross checked if the load spikes happen only on
machines which have these tables.
> As an aside, for the amount of reads/writes you're doing, I've found
> usin
Hi Garo,
Did you put the commit log on its own drive? Spiking CPU during stalls
is a symptom of not doing that. The commitlog is very latency
sensitive, even under low load. Do be sure you're using the deadline
or noop scheduler for that reason, too.
-Mark
On Fri, Jul 22, 2016 at 4:44 PM, Juho M
