On Wed, Jan 22, 2014 at 11:35 AM, John Watson wrote:
> I thought PrintFLSStatistics was necessary for determining heap
> fragmentation? Or is it possible to see that without it as well?
>
I've found that easier parsing is more important than tracking indicators
of fragmentation.
Perm-Gen stays
LCS does create a lot of SSTables unfortunately. The nodes are keeping
up on compactions though.
This started after starting to read from a CF that has tombstones in its rows.
What's even more concerning, is it's continuing even after stopping
reads and dropping that CF.
On Wed, Jan 22, 2014 at
I thought PrintFLSStatistics was necessary for determining heap
fragmentation? Or is it possible to see that without it as well?
Perm-Gen stays steady, but I'll enable it anyway to see if it has any affect.
Thanks,
John
On Wed, Jan 22, 2014 at 8:34 AM, Lee Mighdoll wrote:
> I don't recommend P
I don't recommend PrintFLSStatistics=1, it makes the gc logs hard to
mechanically parse. Because of that, I can't easily tell whether you're in
the same situation we found. But just in case, try setting
+CMSClassUnloadingEnabled. There's an issue related to JMX in DSE that
prevents effective old
SSTable count: 365
Your sstable counts are too many... don't know what is the best count
should be but for my experience, anything below 20 are good. Is your
compaction running?
I read on a few blog on how should we read cfhistograms, but never really
understood fully. Anyone care to explain usi
