> Right now there is a one-to-one mapping between memtables and SSTables. > Instead of that, would it be possible to have one giant memtable for each > Cassandra instance, with partial flushing to SSTs?
I think a complication here is that, although I agree things need to be easier to tweak at least for the common case, I'm pretty sure you'd still want to retain the ability to individually control how flushing happens on a per-cf basis in order to cater to different workloads that benefit from different flushing behavior. I suspect the main concern here may be that there is a desire to have better overal control over how flushing happens and when writes start blocking, rather than necessarily implying that there can't be more than one memtable (the ticket Stu posted seems to address one such means of control). -- / Peter Schuller
