James Howe created CASSANDRA-11995:
--------------------------------------

             Summary: Commitlog replaced with all NULs
                 Key: CASSANDRA-11995
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11995
             Project: Cassandra
          Issue Type: Bug
          Components: Core
         Environment: Windows 10 Enterprise 1511
DataStax Cassandra Community Server 2.2.3
            Reporter: James Howe


I noticed this morning that Cassandra was failing to start, after being shut 
down on Friday.
{code}
ERROR 09:13:37 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 
Community\data\commitlog\CommitLog-5-1465571056722.log
        at 
org.apache.cassandra.db.commitlog.CommitLogReplayer.handleReplayError(CommitLogReplayer.java:622)
 [apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:302)
 [apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.db.commitlog.CommitLogReplayer.recover(CommitLogReplayer.java:147)
 [apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:189) 
[apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:169) 
[apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:273) 
[apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:513) 
[apache-cassandra-2.2.3.jar:2.2.3]
        at 
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:622) 
[apache-cassandra-2.2.3.jar:2.2.3]
{code}
Checking the referenced file reveals it comprises 33554432 NUL bytes.
No logs (stdout, stderr, prunsrv) from the shutdown show any other issues and 
appear exactly as normal.



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

Reply via email to