Tyler, thanks for explanation!
So commit segment can contain both data from flushed table A and non-flushed
table B.How is it replayed on start up? Does C* skip portions belonging to
table A that already were written to SSTable?
Regards, Vlad
On Tuesday, March 1, 2016 11:37 PM, Tyler Hobbs
It would be nice to get this info into the doc or at least a blog post.
-- Jack Krupansky
On Tue, Mar 1, 2016 at 4:37 PM, Tyler Hobbs wrote:
>
> On Tue, Mar 1, 2016 at 6:13 AM, Vlad wrote:
>
>> So commit log can't keep more than memtable size, why is difference in
>> commit log and memtables s
On Tue, Mar 1, 2016 at 6:13 AM, Vlad wrote:
> So commit log can't keep more than memtable size, why is difference in
> commit log and memtables sizes?
In order to purge a commitlog segment, *all* memtables that contain data
from that segment must be flushed to disk.
Suppose you have two tables
up to the next nearest
segment multiple and flushes memtables to disk for the oldest commitlog
segments, removing those log segments.
My question is what is meaning of commit log size being much more than
memtables size.
>From manual: "Cassandra flushes memtables to disk, creating SSTab
Hi Maxim,
Sorry for the late reply but I was away for a course. Lower the
memtable_flush_after_mins for your low traffic CFs. If in the meantime you
upgraded to 1.0 (which by the way 1.0.3 for me ended not working and me
converting a lot of data to it) I think there was a discussion you sent me
on
Alexandru, Jeremiah --
what setting needs to be tweaked, and what's the recommended value?
I observed similar behavior this morning.
Maxim
On 11/28/2011 2:53 PM, Jeremiah Jordan wrote:
Yes, the low volume memtables are causing the problem. Lower the
thresholds for those tables if you don't
Ok, thanks!
On Mon, Nov 28, 2011 at 8:53 PM, Jeremiah Jordan <
jeremiah.jor...@morningstar.com> wrote:
> Yes, the low volume memtables are causing the problem. Lower the
> thresholds for those tables if you don't want the commit logs to go crazy.
>
> -Jeremiah
>
>
> On 11/28/2011 11:11 AM, Alexa
Yes, the low volume memtables are causing the problem. Lower the
thresholds for those tables if you don't want the commit logs to go crazy.
-Jeremiah
On 11/28/2011 11:11 AM, Alexandru Dan Sicoe wrote:
Hello everyone,
4 node Cassandra 0.8.5 cluster with RF=2, replica placement strategy =
Sim
Hello everyone,
4 node Cassandra 0.8.5 cluster with RF=2, replica placement strategy =
SimpleStartegy, write consistency level = ANY, memtable_flush_after_mins
=1440; memtable_operations_in_millions=0.1; memtable_throughput_in_mb = 40;
max_compaction_threshold =32; min_compaction_threshold =4;
I
