cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10155) 2i key cache load fails
Date Wed, 26 Aug 2015 19:47:45 GMT


Ariel Weisberg commented on CASSANDRA-10155:

The fail may go deeper than just filenames.

I copied KeyCacheCQLTest from Robert's in progress work to test saving and loading with a

I added 
to the end of KeyCacheCQLTest.test2iKeyCachePaths and got an exception
java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
	at java.util.ArrayList.rangeCheck( ~[na:1.8.0_51]
	at java.util.ArrayList.get( ~[na:1.8.0_51]
	at org.apache.cassandra.db.ClusteringPrefix$Serializer.valuesWithoutSizeSerializedSize(
	at org.apache.cassandra.db.Clustering$Serializer.serializedSize( ~[main/:na]
	at org.apache.cassandra.db.ClusteringPrefix$Serializer.serializedSize(
	at org.apache.cassandra.db.Serializers$1.serializedSize( ~[main/:na]
	at org.apache.cassandra.db.Serializers$1.serializedSize( ~[main/:na]
	at org.apache.cassandra.db.RowIndexEntry$IndexedEntry.promotedSize(
	at org.apache.cassandra.db.RowIndexEntry$Serializer.serialize( ~[main/:na]
	at org.apache.cassandra.service.CacheService$KeyCacheSerializer.serialize(
	at org.apache.cassandra.service.CacheService$KeyCacheSerializer.serialize(
	at org.apache.cassandra.cache.AutoSavingCache$Writer.saveCache(
	at org.apache.cassandra.db.compaction.CompactionManager$
	at java.util.concurrent.Executors$ ~[na:1.8.0_51]
	at ~[na:1.8.0_51]
	at java.util.concurrent.ThreadPoolExecutor.runWorker( ~[na:1.8.0_51]
	at java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_51]
	at [na:1.8.0_51]

Digging into this one now.

> 2i key cache load fails
> -----------------------
>                 Key: CASSANDRA-10155
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>            Assignee: Ariel Weisberg
>             Fix For: 2.1.9, 3.0.0 rc1, 2.2.2
> 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