You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2011/02/03 19:41:29 UTC
[jira] Reopened: (CASSANDRA-2102) saved row cache doesn't save the
cache
[ https://issues.apache.org/jira/browse/CASSANDRA-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew F. Dennis reopened CASSANDRA-2102:
------------------------------------------
Assignee: Matthew F. Dennis
not really a duplicate.
This deals with writing the cache correctly.
CASSANDRA-2076 should better handle in general when a cache file is corrupt.
> 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