cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew F. Dennis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-2102) saved row cache doesn't save the cache
Date Wed, 02 Feb 2011 22:53:29 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Matthew F. Dennis updated CASSANDRA-2102:
-----------------------------------------

    Attachment: 2102-cassandra-0.7.txt

attached patch switches to saving tokens to disk instead of keys, removes DecoratedKey.key
from the entries in caches (fixing the bug and reducing memory consumption) and versions (kind
of) the saved cache files.

> saved row cache doesn't save the cache
> --------------------------------------
>
>                 Key: CASSANDRA-2102
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2102
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.7.0
>            Reporter: Matthew F. Dennis
>            Assignee: Matthew F. Dennis
>             Fix For: 0.7.2
>
>         Attachments: 2102-cassandra-0.7.txt
>
>
> saving row caches works by periodically iterating of the keySet() on the caches and writing
the keys for the cached contents to disk.  The cache keys are DecoratedKeys.  DecoratedKeys
contain a Token token and a ByteBuffer key.  The underlying buffer on the key gets reused
so the contents change.  This means that all the cache entries have distinct tokens but only
a handful of distinct key values.  This means that when the cache is loaded you only end up
loading a handful of keys instead of the ones actually in your cache.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message