cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10155) 2i key cache load fails
Date Sun, 23 Aug 2015 10:17:45 GMT


Robert Stupp commented on CASSANDRA-10155:

Right, cfName is different for base table and 2i.
But the only parameter to {{AutoSavingCache#getCacheDataPath}}/{{getCacheCrcPath}} is cfId
- so {{DatabaseDescriptor.getSerializedCachePath}} can only return the file name for the base
table. I.e. a {{AutoSavingCache#loadSaved}} will access the same file for base table and 2i

> 2i key cache load fails
> -----------------------
>                 Key: CASSANDRA-10155
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>             Fix For: 3.0.0 rc1
> CASSANDRA-9265 changed how key cache content is serialized to disk. It uses {{UUID cfId}}
to generate the file path for each {{ColumnFamilyStore}}.
> Since {{cfId}} of a secondary index is the same as for the base table, the key-cache
files for 2i's and the base are the same. This will/may lead to deserialization failures on
restart for tables with at least one 2i.
> /cc [~aweisberg] [~danchia]

This message was sent by Atlassian JIRA

View raw message