Please send an email to "user-unsubscr...@cassandra.apache.org" to
unsubscribe from this mailing list.
On 04/08/2022 18:29, Dathan Vance Pattishall wrote:
unsubscribe
unsubscribe
The only messages in OS system log were exactly the same as daemon.log. The
hosts did not shut down, only the Cassandra service stopped. So dmesg has
nothing.
The amount of data being written is not that great and GC times are always <1s.
The only visible error-type messages are related to
Generally speaking, I've seen Cassandra process stopping for the
following reasons:
OOM killer
JVM OOM
Received a signal, such as SIGTERM and SIGKILL
File IO error when disk_failure_policy or commit_failure_policy is
set to die
Hardware issues, such as memory corruption,
Hulloa all,
Service on two nodes stopped yesterday and I can find nothing to indicate why.
I have checked Cassandra system.logs, gc.logs and debug.logs as well as OS logs
and all I can see is the following - which is far from helpful:
DAEMON.LOG
Aug 3 11:39:12 cassandra19 systemd[1]:
