Drew Kutcharian created CASSANDRA-5252:
------------------------------------------
Summary: Starting Cassandra throws EOF while reading saved cache
Key: CASSANDRA-5252
URL: https://issues.apache.org/jira/browse/CASSANDRA-5252
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Drew Kutcharian
Assignee: Dave Brosius
Priority: Minor
Fix For: 1.2.1
Attachments: data.zip
Currently seeing nodes throw an EOF while reading a saved cache on the system
schema when starting cassandra
WARN 14:25:54,896 error reading saved cache
/ssd/saved_caches/system-schema_columns-KeyCache-b.db
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:392)
at
org.apache.cassandra.utils.ByteBufferUtil.readWithLength(ByteBufferUtil.java:349)
at
org.apache.cassandra.service.CacheService$KeyCacheSerializer.deserialize(CacheService.java:378)
at
org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:144)
at
org.apache.cassandra.db.ColumnFamilyStore.<init>(ColumnFamilyStore.java:278)
at
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:393)
at
org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(ColumnFamilyStore.java:365)
at org.apache.cassandra.db.Table.initCf(Table.java:334)
at org.apache.cassandra.db.Table.<init>(Table.java:272)
at org.apache.cassandra.db.Table.open(Table.java:102)
at org.apache.cassandra.db.Table.open(Table.java:80)
at org.apache.cassandra.db.SystemTable.checkHealth(SystemTable.java:320)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:203)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:395)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:438)
to reproduce delete all data files, start a cluster, leave cluster up long
enough to build a cache. nodetool drain, kill cassandra process. start
cassandra process in foreground and note EOF thrown (see above for stack trace)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
