Mattias W created CASSANDRA-12607:
-------------------------------------

             Summary: The cassandra commit log corrupted by restart even if no 
write operations in hours
                 Key: CASSANDRA-12607
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12607
             Project: Cassandra
          Issue Type: Bug
         Environment: windows 10, 16 gb
            Reporter: Mattias W
             Fix For: 3.x


This is the 3rd time my commitlog is corrupted, and the server refuses to 
start. What worries me is that I get these error issues even if no update were 
made to the database.

The last time, the computer were restarted by Windows update, and I detected 
the problem immediately. 

The problems is solved by deleting the commitlog files (ok on my development 
system)

My config says that commitlog are synced every 10s seconds, so how can a file 
be corrupt unless a crash occurs within these 10 seconds?

Is this a Cassandra bug? Or by design, i.e. bad design?

I am using 3.4 on Windows 10, Datastax installer.

In the stdout log, the last part is

{noformat}
INFO  06:17:39 Replaying C:\Program 
Files\DataStax-DDC\data\commitlog\CommitLog-6-1471353812251.log, C:\Program 
Files\DataStax-DDC\data\commitlog\CommitLog-6-1471353812252.log, C:\Program 
Files\DataStax-DDC\data\commitlog\CommitLog-6-1471411951134.log, C:\Program 
Files\DataStax-DDC\data\commitlog\CommitLog-6-1471454506802.log, C:\Program 
Files\DataStax-DDC\data\commitlog\CommitLog-6-1471532812678.log
ERROR 06:17:39 Exiting due to error while processing commit log during 
initialization.
org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: 
Could not read commit log descriptor in file C:\Program 
Files\DataStax-DDC\data\commitlog\CommitLog-6-1471353812252.log
    at 
org.apache.cassandra.db.commitlog.CommitLogReplayer.handleReplayError(CommitLogReplayer.java:611)
 [apache-cassandra-3.4.0.jar:3.4.0]
    at 
org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:373)
 [apache-cassandra-3.4.0.jar:3.4.0]
    at 
org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:236)
 [apache-cassandra-3.4.0.jar:3.4.0]
    at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:192) 
[apache-cassandra-3.4.0.jar:3.4.0]
    at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:172) 
[apache-cassandra-3.4.0.jar:3.4.0]
    at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:283) 
[apache-cassandra-3.4.0.jar:3.4.0]
    at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:551) 
[apache-cassandra-3.4.0.jar:3.4.0]
    at 
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:680) 
[apache-cassandra-3.4.0.jar:3.4.0]




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to