[jira] [Commented] (CASSANDRA-9776) Tombstone Compaction Not Getting Triggered on a single SSTable even when the % of Droppable > 85%

["Marcus Eriksson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621781#comment-14621781 ] 

Marcus Eriksson commented on CASSANDRA-9776:
--------------------------------------------

If the node is not getting any writes, it wont trigger compactions at all (until CASSANDRA-9592), did you write to your node or just leave it alone?

> Tombstone Compaction Not Getting Triggered on a single SSTable even when the % of Droppable > 85%
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9776
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9776
>             Project: Cassandra
>          Issue Type: New Feature
>         Environment: RHEL
> Apache Cassandra v 2.0.14
>            Reporter: Parth Setya
>             Fix For: 2.0.14
>
>
> The following steps can be used to Replicate the Issue:
> 1. Reduce gc_grace_seconds to 18000
> 2. Set tombstone_compaction_interval to 1 day
> 3. Insert 9 Million Rows
> 4. Delete 9 Million Rows
> 5. Insert 1 Million Rows
> 6. Run Major Compaction so that the Tombstones for 9 million rows and expiring columns for 1 million rows are in the same SStable.(In may case the size of the resultant sstable was 963M)
> Note: I also ran "nodetool cfstats" command and the found that the number of keys in the CF to be 10000000(as expected)
> Tombstone Compaction on the resultant SSTable should have been triggered after 1 day after the creation of that Table but nothing happened for > 2 days.
> After 3 days I ran major compaction the size of the table was reduced to 213M.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)