[
https://issues.apache.org/jira/browse/CASSANDRA-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698088#comment-13698088
]
Eric Lubow commented on CASSANDRA-4730:
---------------------------------------
The one thing I would like to advocate against is that Cassandra should not
fail to start if there is a corrupt CommitLog. It should throw a nasty error
in the logs but not fail to load entirely. I think the default behavior should
be leaning towards availability and the server should be able to start just
ignoring the corrupt CommitLog.
> CommitLogReplayer should report the bad CRC checksum in the log
> ---------------------------------------------------------------
>
> Key: CASSANDRA-4730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4730
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.5
> Environment: Cassandra 1.1.5
> Reporter: Arya Goudarzi
>
> If commit log isn't fully fsynced, the record which fails the checksum is not
> replayed do this logic. It would be beneficial to log that as an error so
> that user can know easily what happened.
> "./src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java" line
> 188 of 287 --65%-- col 54
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
