> sstables waiting for the GC to trigger actual file removal. *However*, > and this is what I meant with my follow-up, that still does not > explain the data from her post unless 'nodetool ring' reports total > sstable size rather than the total size of live sstables.
As far as I can tell, the information 'nodetool ring' prints comes from SSTableTracker's liveSize. This seems to be updated in replace() which is used by the compaction manager after compaction. So I do believe 'nodetool ring' should *not* include the size of sstables that have been compacted, regardless of GC and whether they still remain on disk. -- / Peter Schuller
