Re: Compaction issues, 2.0.12

2015-07-07 Thread Jeff Williams
Thanks Rob, Jeff. I have updated the Jira issue with my information. On 6 July 2015 at 23:46, Jeff Ferland j...@tubularlabs.com 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

Re: Compaction issues, 2.0.12

2015-07-06 Thread Jeff Williams
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

2015-07-06 Thread Robert Coli
On Mon, Jul 6, 2015 at 1:46 PM, Jeff Williams je...@wherethebitsroam.com 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

Re: Compaction issues, 2.0.12

2015-07-06 Thread Robert Coli
On Mon, Jul 6, 2015 at 7:25 AM, Jeff Williams je...@wherethebitsroam.com 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!

Re: Compaction issues, 2.0.12

2015-07-06 Thread Jeff Ferland
I’ve seen the same thing: https://issues.apache.org/jira/browse/CASSANDRA-9577 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, Robert

Compaction issues, 2.0.12

2015-07-06 Thread Jeff Williams
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

Re: Compaction issues

2013-10-24 Thread Russ Garrett
On 23 October 2013 21:25, Aaron Morton aa...@thelastpickle.com wrote: Is there ever a time when the pending count is non zero but nodetool compactionstats does not show any running tasks ? No - but there are times when the number of running compaction processes is less than

Compaction issues

2013-10-23 Thread Russ Garrett
Hi, We have a cluster which we've recently moved to use LeveledCompactionStrategy. We were experiencing some disk space issues, so we added two additional nodes temporarily to aid compaction. Once the compaction had completed on all nodes, we decommissioned the two temporary nodes. All nodes now

Re: Compaction issues

2013-10-23 Thread Michael Theroux
One more note, When we did this conversion, we were on Cassandra 1.1.X. You didn't mention what version of Cassandra you were running, Thanks, -Mike On Oct 23, 2013, at 10:05 AM, Michael Theroux wrote: When we made a similar move, for an unknown reason (I didn't hear any feedback from the

Re: Compaction issues

2013-10-23 Thread Russ Garrett
On 23 October 2013 15:05, Michael Theroux mthero...@yahoo.com wrote: When we made a similar move, for an unknown reason (I didn't hear any feedback from the list when I asked why this might be), compaction didn't start after we moved from SizedTiered to leveled compaction until I ran

Re: Compaction issues

2013-10-23 Thread Aaron Morton
Also, there are plenty of compactions running - it just seems like the number of pending tasks is never affected. Is there ever a time when the pending count is non zero but nodetool compactionstats does not show any running tasks ? If compaction cannot keep up you may be generating data