cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peng Xiao" <>
Subject 回复:RE: Row Cache hit issue
Date Wed, 20 Sep 2017 05:47:12 GMT
Thanks All.

------------------ 原始邮件 ------------------
发件人: "Steinmaurer, Thomas";<>;
发送时间: 2017年9月20日(星期三) 中午1:38
收件人: ""<>;

主题: RE: Row Cache hit issue

additionally, with saved (key) caches, we had some sort of corruption (I think, for whatever
reason) once. So, if you  see something like that upon Cassandra startup:
INFO [main] 2017-01-04 15:38:58,772 (line 114) reading saved cache /var/opt/xxx/cassandra/saved_caches/ks-cf-KeyCache-b.db
ERROR [main] 2017-01-04 15:38:58,891 (line 571) Exception encountered
during startup
java.lang.OutOfMemoryError: Java heap space
                at java.util.ArrayList.<init>(
                at org.apache.cassandra.db.RowIndexEntry$Serializer.deserialize(
                at org.apache.cassandra.service.CacheService$KeyCacheSerializer.deserialize(
                at org.apache.cassandra.cache.AutoSavingCache.loadSaved(
                at org.apache.cassandra.db.ColumnFamilyStore.<init>(
                at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(
                at org.apache.cassandra.db.ColumnFamilyStore.createColumnFamilyStore(
                at org.apache.cassandra.db.Keyspace.initCf(
                at org.apache.cassandra.db.Keyspace.<init>(
                at org.apache.cassandra.service.CassandraDaemon.setup(
                at org.apache.cassandra.service.CassandraDaemon.activate(
                at org.apache.cassandra.service.CassandraDaemon.main(
resulting in Cassandra going OOM, with a “reading saved cache” log entry close before
the OOM, you may have hit some sort  of corruption. Workaround is to physically delete the
saved cache file and Cassandra will start up just fine.
From: Dikang Gu [] 
 Sent: Mittwoch, 20. September 2017 06:06
 To: cassandra <>
 Subject: Re: Row Cache hit issue
Hi Peng,
C* periodically saves cache to disk, to solve cold start problem. If row_cache_save_period=0,
it means C* does not save cache to disk. But the cache is still working, if it's enabled in
table schema, just the cache will be empty after restart.
On Tue, Sep 19, 2017 at 8:27 PM, Peng Xiao <> wrote:
And we are using C* 2.1.18.
------------------ Original ------------------
From:  "我自己的邮箱";<>;
Date:  Wed, Sep 20, 2017 11:27 AM
To:  "user"<>;
Subject:  Row Cache hit issue
Dear All,
The default row_cache_save_period=0,looks Row Cache does not work in this situation?
but we can still see the row cache hit.
Row Cache              : entries 202787, size 100 MB, capacity 100 MB, 3095293 hits, 6796801
requests, 0.455 recent hit rate, 0 save period in seconds
Could anyone please explain this?
Peng Xiao

 The contents of this e-mail are intended for the named addressee only. It contains information
that may be confidential. Unless you are the named addressee or an authorized designee, you
may not copy or use it, or disclose it to anyone else. If you received  it in error please
notify us immediately and then destroy it. Dynatrace Austria GmbH (registration number FN
91482h) is a company registered in Linz whose registered office is at 4040 Linz, Austria,
Freistädterstraße 313
View raw message