Thanks Erick!
I will check with the owners of this keyspace, hoping to find the culprit.
If they won't come up with anything, is there a way to read the key cache
file? (as I understand it's a binary file)
On another note, there's actually another keyspace I missed to point out on
which I found a
> Specifically for the NegativeArraySizeException, what's happening is that
> the keyLength is so huge that it blows up MAX_UNSIGNED_SHORT so it looks
> like it's a negative value. Someone will correct me if I got that wrong but
> the "Key length longer than max" error confirms that.
>
Is it possi
Oh, I just saw the example. Never mind. :)
>
> Does anyone perhaps have an idea on what could've gone wrong here?
> Could it be just a calculation error on startup?
>
Specifically for the NegativeArraySizeException, what's happening is that
the keyLength is so huge that it blows up MAX_UNSIGNED_SHORT so it looks
like it's a negative value.
Hi again,
Does anyone perhaps have an idea on what could've gone wrong here?
Could it be just a calculation error on startup?
Thanks!
On Sun, Jan 26, 2020 at 5:57 PM Shalom Sagges
wrote:
> Hi Jeff,
>
> It is happening on multiple servers and even on different DCs.
> The schema contains two key
Hi Jeff,
It is happening on multiple servers and even on different DCs.
The schema contains two keyspaces as follows:
CREATE KEYSPACE ks1 WITH replication = {'class': 'NetworkTopologyStrategy',
'DC1': '3', 'DC2': '3'} AND durable_writes = true;
CREATE TABLE ks1.tbl1 (
account_id text,
m
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
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
