Hi Jon,
I was able to get a heapdump. - I created a JIRA and attached as much as
details as possible.
https://issues.apache.org/jira/browse/CASSANDRA-14239
The heapdump is 42GB in Size. I will keep it - if you need more information
please don't hesitate to let me know.
thanks,
Jürgen
2018-02-09
The main overhead is that each table locks 1MB of Java heap, so if you have
1000 tables it will use 1GB of RAM just for managing the tables, even if they
are empty.
--
Jacques-Henri Berthemet
From: Alaa Zubaidi (PDF) [mailto:alaa.zuba...@pdf.com]
Sent: Friday, February 16, 2018 1:05 AM
To: user
Hi All
I saw something curious when I restarted our cluster following a full shutdown
whereby the result of calling nodetool getendpoints showed inconsistent results
as each node was started in turn.
Prior to shutdown, we had the following:
$ nodetool status
Datacenter: dc1
===
Sta
Hi,
I am using cassandra version 2.0 . My goal is to do cassandra client to
node security using SSL with my self-signed CA.
What would be the recommended procedure for enabling SSL on cassandra
version 2.0.17 .
Thanks,
Prachi
http://thelastpickle.com/blog/2015/09/30/hardening-cassandra-step-by-step-part-1-server-to-server.html
https://www.youtube.com/watch?v=CKt0XVPogf4
(2.0 is getting pretty old and isn't supported, you may want to consider
upgrading; 2.1 would be the smallest change and least risk, but it, too, is
n
PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--
The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after thi
PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--
The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after thi
Thanks. Yeah, it appears this would only be doable if we didn't have vnodes
and used old single token clusters. I guess Priam has something where you
increase the cluster by whole number multiples. Then there's the issue of
doing quorum read/writes if there suddenly is a new replica range with
grey
