Hi,there are following parameters in casansdra.yaml: memtable_total_space_in_mb (1/4 of heap, e.g. 512MB)- Specifies the total memory used for all memtables on a node. commitlog_total_space_in_mb (8GB) - Total space used for commit logs. If the used space goes above this value, Cassandra rounds 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 SSTables when the >commit log space threshold has been exceeded.", but as far as I understand >memtables are also flushed when too much memtables are used and anyway >unflashed size can't be more than memtable size in memory. So commit log >can't keep more than memtable size, why is difference in commit log and >memtables sizes?
Regards, Vlad
