Enforce best practices to save yourself and your organization from system debt
brought on by bad practices compounded by bad practices because some people are
beyond reproach. See bad practices as they are and correct them.
TLDR;
I still stick with my initial recommendations. What you are talki
On Wed, Mar 14, 2018 at 2:40 PM, Durity, Sean R
wrote:
> The DataStax documentation is far superior to the Apache Cassandra attempts.
> Apache is just poor with holes all over, goofy examples, etc. It would take
> a team of people working full time to try and catch up with DataStax. I have
> met t
Jeff,
I think additionally the reason might also be that the keyspace was
using TimeWindowCompactionStrategy
with 1 day bucket; however the writes very quite rapid and no automatic
compaction was working.
I would think changing strategy to SizeTiered would also solve this problem?
- Affan
On
TWCS does SizeTieredCompaction within the window, so it’s not likely to make a
difference. I’m +1’ing what Jeff said, 128ms memtable_flush_period_in_ms is
almost certainly your problem, unless you’ve changed other settings and haven’t
told us about them.
> On Mar 15, 2018, at 9:54 AM, Affan
No it did solve the problem, as Faraz mentioned but I am still not sure
about whats the underlying cause. Is 0ms really correct? how do we setu a
flush period?
- Affan
On Thu, Mar 15, 2018 at 10:00 PM, Jon Haddad wrote:
> TWCS does SizeTieredCompaction within the window, so it’s not likely to
>
Generally speaking, you don't need to. I almost never do. I've only set
it in situations where I've had a large number of tables and I want to
avoid a lot of flushing when commit log segments are removed.
Setting it to 128 milliseconds means it's flushing 8 times per second,
which gives no benef
Hello!
We are experiencing problems with Cassandra 2.2.8.
There is a cluster with 3 nodes.
Problematic keyspace has RF=3 and contains 3 tables (current table sizes:
1Gb, 700Mb, 12Kb).
Several times per day there are bursts of "READ messages were dropped ...
for internal timeout" messages in logs
