You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2014/05/01 12:09:14 UTC

[jira] [Commented] (CASSANDRA-7125) Fail to start by default if Commit Log fails to validate any messages

    [ https://issues.apache.org/jira/browse/CASSANDRA-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986474#comment-13986474 ] 

Sylvain Lebresne commented on CASSANDRA-7125:
---------------------------------------------

bq. and introduce a cassandra.yaml option that permits overriding the default behaviour

<bikeshedding>I feel a command line override flag (i.e. something like -Dcassandra.commitlog.skipbrokenentries=true) would be more appropriate here</bikeshedding>. But agreed on  changing the default behavior otherwise. 

> 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.0
>
>
> 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)