I have a assumption that, lots of pending compaction tasks jam the memory
and raise full gc. The full chokes the process and slows down compaction.
And this causes more pending compaction tasks and more pressure on memory.
Is there a method to list the concrete details of pending compaction tasks?
On Tue, Jan 12, 2016 at 11:41 AM, Robert Coli <rc...@eventbrite.com> wrote:
> The lines you are looking for look like this :
>
> INFO [CompactionExecutor:48] 2016-01-12 09:07:59,995 CompactionTask.java
> (line 120) Compacting
> [SSTableReader(path='/usr/local/cassandra/data/system/sstable_activity/system-sstable_activity-jb-4959-Data.db'),
> SSTableReader(path='/usr/local/cassandra/data/system/sstable_activity/system-sstable_activity-jb-4960-Data.db'),
> SSTableReader(path='/usr/local/cassandra/data/system/sstable_activity/system-sstable_activity-jb-4961-Data.db'),
> SSTableReader(path='/usr/local/cassandra/data/system/sstable_activity/system-sstable_activity-jb-4962-Data.db')]
>
> and
>
> INFO [CompactionExecutor:47] 2016-01-12 04:06:43,946 CompactionTask.java
> (line 299) Compacted 4 sstables to
> [/usr/local/cassandra/data/system/compaction_history/system-compaction_history-jb-3532,].
> 14,413 bytes to 13,334 (~92% of original) in 52,135ms = 0.000244MB/s. 156
> total partitions merged to 149. Partition merge counts were {1:156, }
>
> There are only 4 of the compaction completed messages in the log you
> attached, tiny ones.
>
> The log doesn't look like much compaction is occurring?
>
> =Rob
>
>
--
*陈硕* *Shuo Chen*
chenatu2...@gmail.com
chens...@whaty.com
