489MB key seems huge. Unlikely it’s really that large.
If it’s happening on multiple servers it’d be interesting to see the schema
and/or saved cache file if it’s not incredibly sensitive
> On Jan 23, 2020, at 3:48 AM, Shalom Sagges wrote:
>
>
> Hi All,
>
> Cassandra 3.11.4.
> On one of our clusters, during startup, I see two types of "Harmless error"
> notification regarding the keycache:
>
> Server 1:
>
> INFO [pool-3-thread-1] 2020-01-23 04:34:46,167 AutoSavingCache.java:263 -
> Harmless error reading saved cache /path/to/saved_caches/KeyCache-e.db
> java.lang.NegativeArraySizeException: null
> at
> org.apache.cassandra.utils.ByteBufferUtil.read(ByteBufferUtil.java:401)
> at
> org.apache.cassandra.service.CacheService$KeyCacheSerializer.deserialize(CacheService.java:472)
> at
> org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:220)
> at
> org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:165)
> at
> org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:161)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> INFO [pool-3-thread-1] 2020-01-23 04:34:46,168 AutoSavingCache.java:174 -
> Completed loading (188 ms; 10916 keys) KeyCache cache
>
>
> Server 2:
>
> INFO [pool-3-thread-1] 2020-01-15 11:18:35,797 AutoSavingCache.java:263 -
> Harmless error reading saved cache /path/to/saved_caches//KeyCache-e.db
> java.io.IOException: Corrupted key cache. Key length of 489735494 is longer
> than maximum of 65535
> at
> org.apache.cassandra.service.CacheService$KeyCacheSerializer.deserialize(CacheService.java:469)
> at
> org.apache.cassandra.cache.AutoSavingCache.loadSaved(AutoSavingCache.java:220)
> at
> org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:165)
> at
> org.apache.cassandra.cache.AutoSavingCache$3.call(AutoSavingCache.java:161)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> INFO [pool-3-thread-1] 2020-01-15 11:18:35,799 AutoSavingCache.java:174 -
> Completed loading (285 ms; 20681 keys) KeyCache cache
>
> The KeyCache size is a lot less than max default (100MB). So does this mean
> that the key itself is the culprit?
>
> I'd really appreciate some guidance on what this message actually means in
> the logs during startup and what problems may arise from it.
> I see that one of the nodes experiences high CPU load and even gets kernel
> panic from time to time, so I want to understand if the above may cause such
> issues.
>
> Thanks a lot!
>
