Or if you're doing a high volume of writes, then your flushed file size may be completely determined by other CFs that have consumed the commitlog size, forcing any memtables whose commitlog is being delete to be forced to disk.
On Wed, Oct 28, 2015 at 2:51 PM, Jeff Jirsa <jeff.ji...@crowdstrike.com> wrote: > It’s worth mentioning that initial flushed file size is typically > determined by memtable_cleanup_threshold and the memtable space options > (memtable_heap_space_in_mb, memtable_offheap_space_in_mb, depending on > memtable_allocation_type) > > > > From: Nate McCall > Reply-To: "user@cassandra.apache.org" > Date: Wednesday, October 28, 2015 at 11:45 AM > To: Cassandra Users > Subject: Re: memtable flush size with LCS > > > do you mean that this property is ignored at memtable flush time, and so >> memtables are already allowed to be much larger than sstable_size_in_mb? >> > > Yes, 'sstable_size_in_mb' plays no part in the flush process. Flushing is > based on solely on runtime activity and the file size is determined by > whatever was in the memtable at that time. > > > > -- > ----------------- > Nate McCall > Austin, TX > @zznate > > Co-Founder & Sr. Technical Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com >
