Hi, Are you referring to the binary_memtable_throughput_in_mb which is a global parameter or the per col fam specific memtable_throughput_in_mb? The former is set to 256 and we dont override the default col fam specific value. Would just re-setting the global binary_memtable_throughput_in_mb to something like 64 be enough? Thanks!
On Fri, May 13, 2011 at 10:30 PM, mcasandra <mohitanch...@gmail.com> wrote: > 5G in one hour is actually very low. Something else is wrong. Peter pointed > to something related to memtable size could be causing this problem, can > you > turn down memtable_throughput and see if that helps. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Commitlog-Disk-Full-tp6356797p6362301.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >