Riccardo Paoli created CASSANDRA-14786:
------------------------------------------
Summary: Attempted to delete non-existing file CommitLog
Key: CASSANDRA-14786
URL: https://issues.apache.org/jira/browse/CASSANDRA-14786
Project: Cassandra
Issue Type: Bug
Environment: RedHat 6.8 x64
Apache Cassandra 2.2.9
Reporter: Riccardo Paoli
Attachments: Cassandra_2209.zip
Hi all,
we write here for the first time so forgive us if we forget something.
At one of our customers we have installed some Genesys applications that use a
Cassandra cluster with 3 nodes.
For several weeks, at regular intervals, Cassandra's trials encounter problems
and start shutdown. In particular, the error that is reported on the logs is as
follows:
NODE 2
{code:java}
ERROR [COMMIT-LOG-ALLOCATOR] 2018-09-21 23:05:48,718 CommitLog.java:488 -
Failed managing commit log segments. Commit disk failure policy is stop;
terminating thread
java.lang.AssertionError: attempted to delete non-existing file
CommitLog-5-1537387998650.log
{code}
NODE 1
{code:java}
ERROR [COMMIT-LOG-ALLOCATOR] 2018-09-22 01:04:53,488 CommitLog.java:488 -
Failed managing commit log segments. Commit disk failure policy is stop;
terminating thread
java.lang.AssertionError: attempted to delete non-existing file
CommitLog-5-1537387930979.log
{code}
NODE 3
{code:java}
ERROR [COMMIT-LOG-ALLOCATOR] 2018-09-22 04:31:56,176 CommitLog.java:488 -
Failed managing commit log segments. Commit disk failure policy is stop;
terminating thread
java.lang.AssertionError: attempted to delete non-existing file
CommitLog-5-1537388059095.log
{code}
h6.
Is it possible to understand the cause?
Attached the logs of the 22/09 error and the cluster configuration.
Thanks to the availability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
