Nope, they flush every 5 to 10 minutes.
On Mon, Mar 2, 2015 at 1:13 PM, Daniel Chia wrote:
> Do the tables look like they're being flushed every hour? It seems like
> the setting memtable_flush_after_mins which I believe defaults to 60
> could also affect how often your tables are flushed.
>
> T
Do the tables look like they're being flushed every hour? It seems like the
setting memtable_flush_after_mins which I believe defaults to 60 could also
affect how often your tables are flushed.
Thanks,
Daniel
On Mon, Mar 2, 2015 at 11:49 AM, Dan Kinder wrote:
> I see, thanks for the input. Comp
I see, thanks for the input. Compression is not enabled at the moment, but
I may try increasing that number regardless.
Also I don't think in-memory tables would work since the dataset is
actually quite large. The pattern is more like a given set of rows will
receive many overwriting updates and t
On Fri, Feb 27, 2015 at 2:01 PM, Dan Kinder wrote:
> Theoretically sstable_size_in_mb could be causing it to flush (it's at the
> default 160MB)... though we are flushing well before we hit 160MB. I have
> not tried changing this but we don't necessarily want all the sstables to
> be large anyway
Hi all,
We have a table in Cassandra where we frequently overwrite recent inserts.
Compaction does a fine job with this but ultimately larger memtables would
reduce compactions.
The question is: can we make Cassandra use larger memtables and flush less
frequently? What currently triggers the flus
