Re: Compaction issues, 2.0.12

Thanks Rob, Jeff. I have updated the Jira issue with my information. On 6 July 2015 at 23:46, Jeff Ferland wrote: > I’ve seen the same thing: > https://issues.apache.org/jira/browse/CASSANDRA-9577 > > I’ve had cases where a restart clears the old tables, and I’ve had cases > where a restart cons

Re: Compaction issues, 2.0.12

I’ve seen the same thing: https://issues.apache.org/jira/browse/CASSANDRA-9577 I’ve had cases where a restart clears the old tables, and I’ve had cases where a restart considers the old tables to be live. > On Jul 6, 2015, at 1:51 PM, Rober

Re: Compaction issues, 2.0.12

On Mon, Jul 6, 2015 at 1:46 PM, Jeff Williams wrote: > 1) Cassandra version is 2.0.12. > > 2) Interesting. Looking at JMX org.apache.cassandra.db -> ColumnFamilies > -> trackcontent -> track_content -> Attributes, I get: > > LiveDiskSpaceUsed: 17788740448, i.e. ~17GB > LiveSSTableCount: 3 > Tot

Re: Compaction issues, 2.0.12

Thanks Rob. 1) Cassandra version is 2.0.12. 2) Interesting. Looking at JMX org.apache.cassandra.db -> ColumnFamilies -> trackcontent -> track_content -> Attributes, I get: LiveDiskSpaceUsed: 17788740448, i.e. ~17GB LiveSSTableCount: 3 TotalDiskSpaceUsed: 55714084629, i.e. ~55GB So it obviously

Re: Compaction issues, 2.0.12

On Mon, Jul 6, 2015 at 7:25 AM, Jeff Williams wrote: > So it appears that the 10 sstables that were compacted > to > /var/lib/cassandra/data/trackcontent/track_content/trackcontent-track_content-jb-57372 > are still sitting around, with a couple of them being very large! > Any ideas for what I c

Compaction issues, 2.0.12

Hi, I have a keyspace which is using about 19GB on most nodes in the cluster. However on one node the data directory for the only table in that keyspace now uses 52GB. It seems that old sstables are not removed after compaction. Here is a view of the data directory Data files before compaction (I