cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joaquin Casares (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-3511) Supercolumn key caches are not saved
Date Tue, 20 Dec 2011 00:59:30 GMT

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

Joaquin Casares edited comment on CASSANDRA-3511 at 12/20/11 12:58 AM:
-----------------------------------------------------------------------

http://aep.appspot.com/display/YS0VCvsOzFbkE-72IFOqBm8-URg/

I tried this multiple times and switching the super column family creation order and still
saw all the cache fill up.

On Cassandra 1.0.5.

What happens when you run these scripts on your machine? NOTE: This will drop all of your
Keyspace1 data, you may have to edit that line.
                
      was (Author: j.casares):
    http://aep.appspot.com/display/YS0VCvsOzFbkE-72IFOqBm8-URg/

I tried this multiple times and switching the super column family creation order and still
saw all the cache fill up.

On Cassandra 1.0.5.
                  
> Supercolumn key caches are not saved
> ------------------------------------
>
>                 Key: CASSANDRA-3511
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3511
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.2, 1.0.3
>            Reporter: Radim Kolar
>            Priority: Minor
>              Labels: supercolumns
>         Attachments: failed-to-save-after-load-KeyCache, rapidshare-resultcache-KeyCache
>
>
> cache saving seems to be broken in 1.0.2 and 1.0.3 i have 2 CF in keyspace with enabled
cache saving and only one gets its key cache saved. It worked perfectly in 0.8, both were
saved.
> This one works:
> create column family query2
>   with column_type = 'Standard'
>   and comparator = 'AsciiType'
>   and default_validation_class = 'BytesType'
>   and key_validation_class = 'UTF8Type'
>   and rows_cached = 500.0
>   and row_cache_save_period = 0
>   and row_cache_keys_to_save = 2147483647
>   and keys_cached = 200000.0
>   and key_cache_save_period = 14400
>   and read_repair_chance = 1.0
>   and gc_grace = 864000
>   and min_compaction_threshold = 5
>   and max_compaction_threshold = 10
>   and replicate_on_write = false
>   and row_cache_provider = 'ConcurrentLinkedHashCacheProvider'
>   and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy'
> This does not
> create column family dkb13
>   with column_type = 'Super'
>   and comparator = 'LongType'
>   and subcomparator = 'AsciiType'
>   and default_validation_class = 'BytesType'
>   and key_validation_class = 'UTF8Type'
>   and rows_cached = 600.0
>   and row_cache_save_period = 0
>   and row_cache_keys_to_save = 2147483647
>   and keys_cached = 200000.0
>   and key_cache_save_period = 14400
>   and read_repair_chance = 1.0
>   and gc_grace = 864000
>   and min_compaction_threshold = 5
>   and max_compaction_threshold = 10
>   and replicate_on_write = false
>   and row_cache_provider = 'ConcurrentLinkedHashCacheProvider'
>   and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy'
> in second test system i created these 2 column families and none of them got single cache
key saved. Both have save period 30 seoonds - their cache should save often. Its not that
standard column family works while super does not.
> create column family test1
>   with column_type = 'Standard'
>   and comparator = 'BytesType'
>   and default_validation_class = 'BytesType'
>   and key_validation_class = 'BytesType'
>   and rows_cached = 0.0
>   and row_cache_save_period = 0
>   and row_cache_keys_to_save = 2147483647
>   and keys_cached = 200000.0
>   and key_cache_save_period = 30
>   and read_repair_chance = 1.0
>   and gc_grace = 864000
>   and min_compaction_threshold = 4
>   and max_compaction_threshold = 32
>   and replicate_on_write = true
>   and row_cache_provider = 'SerializingCacheProvider'
>   and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy';
> create column family test2
>   with column_type = 'Standard'
>   and comparator = 'BytesType'
>   and default_validation_class = 'BytesType'
>   and key_validation_class = 'BytesType'
>   and rows_cached = 0.0
>   and row_cache_save_period = 0
>   and row_cache_keys_to_save = 2147483647
>   and keys_cached = 200000.0
>   and key_cache_save_period = 30
>   and read_repair_chance = 1.0
>   and gc_grace = 864000
>   and min_compaction_threshold = 4
>   and max_compaction_threshold = 32
>   and replicate_on_write = true
>   and row_cache_provider = 'SerializingCacheProvider'
>   and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy';
> If this is done on purpose for example cassandra 1.0 is doing some heuristic decision
if cache should be saved or not then it should be removed. Saving cache is fast.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message