[
https://issues.apache.org/jira/browse/CASSANDRA-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026686#comment-14026686
]
sankalp kohli commented on CASSANDRA-7125:
------------------------------------------
something like -Dcassandra.commitlog.skipbrokenentries=true
+1 on this and also to fail the startup. Also what if it fails to load an
sstable on startup specially if stable is created recently? Do we have
something for it?
> Fail to start by default if Commit Log fails to validate any messages
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-7125
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7125
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Labels: correctness
> Fix For: 2.1.1
>
>
> Current behaviour can be pretty dangerous, and also has a tendency to mask
> bugs during development. We should change the behaviour to default to failure
> if anything unexpected happens, and introduce a cassandra.yaml option that
> permits overriding the default behaviour.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
