[jira] [Comment Edited] (CASSANDRA-6654) Droppable tombstones are not being removed from LCS table despite being above 20%

["Keith Wright (JIRA)" <ji...@apache.org>]

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

Keith Wright edited comment on CASSANDRA-6654 at 2/24/14 2:02 PM:
------------------------------------------------------------------

Note that this issue is still occurring and has only gotten worse (now reporting at 31%).  Note that we use differing TTLs depending on rows where the sku_time map has a TTL of 28 days, values at 7 days, and the rest either no TTL or 6 months.

Also note that on a sized tiered table, JMX is reporting a droppable tombstone ratio of 48% (will likely be moving that table to LCS just to ensure data space is reclaimed quickly as it uses a relatively short TTL of a couple days)


was (Author: keithwrightbos):
Note that this issue is still occurring and has only gotten worse (not reporting at 31%).  Note that we use differing TTLs depending on rows where the sku_time map has a TTL of 28 days, values at 7 days, and the rest either no TTL or 6 months.

Also note that on a sized tiered table, JMX is reporting a droppable tombstone ratio of 48% (will likely be moving that table to LCS just to ensure data space is reclaimed quickly as it uses a relatively short TTL of a couple days)

> Droppable tombstones are not being removed from LCS table despite being above 20%
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6654
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6654
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: 1.2.13 VNodes with murmur3
>            Reporter: Keith Wright
>            Assignee: Russ Hatch
>         Attachments: Screen Shot 2014-02-05 at 9.38.20 AM.png
>
>
> JMX is showing that one of our CQL3 LCS tables has a droppable tombstone ratio above 20% and increasing (currently at 28%).  Compactions are not falling behind and we are using the OOTB setting for this feature so I would expect not to go above 20% (will attach screen shot from JMX).   Table description:
> CREATE TABLE global_user (
>   user_id timeuuid,
>   app_id int,
>   type text,
>   name text,
>   extra_param map<text, text>,
>   last timestamp,
>   paid boolean,
>   sku_time map<text, timestamp>,
>   values map<timestamp, float>,
>   PRIMARY KEY (user_id, app_id, type, name)
> ) WITH
>   bloom_filter_fp_chance=0.100000 AND
>   caching='KEYS_ONLY' AND
>   comment='' AND
>   dclocal_read_repair_chance=0.000000 AND
>   gc_grace_seconds=86400 AND
>   read_repair_chance=0.100000 AND
>   replicate_on_write='true' AND
>   populate_io_cache_on_flush='false' AND
>   compaction={'sstable_size_in_mb': '160', 'class': 'LeveledCompactionStrategy'} AND
>   compression={'chunk_length_kb': '8', 'crc_check_chance': '0.1', 'sstable_compression': 'LZ4Compressor'}; 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)