Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 2 Feb 2011 22:51:29 +0000 (UTC)
From: "Matthew F. Dennis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1182798892.6153.1296687089347.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1856211205.6139.1296686609061.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (CASSANDRA-2102) saved row cache doesn't save the
 cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

    Affects Version/s: 0.7.0
        Fix Version/s: 0.7.2

> 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
>
>
> 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