After rolling restart, we are seeing all nodes in the cluster, but still, I
am seeing TOKENS: not present in gossipinfo
/96.xx.xx.xx
generation:1565342394
heartbeat:30093
LOAD:30083:8.7263163447E10
SCHEMA:14:684b2142-327b-30a0-bcaf-b906208bd9b4
DC:8:Xx-EAST-xx
RACK:10:xx-xx-xxx
RELEA
Confirmed, we are not using NVMe
So, this is my interpretation of the error of one of the corrupt files,
full error stack below;
- original exception is this:
Caused by: org.apache.cassandra.io.compress.CorruptBlockException:
(/data/ssd2/data/KeyspaceMetadata/CF_ToIndex/lb-26203-big-Data.db)
Hi.
After update systemd with fixed vulnerability
https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service
does not start correctly.
How to fix it? It may be necessary to add a real service unit for systemd ?
system
