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

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reopened CASSANDRA-7125:
---------------------------------------


We shouldn't halt startup for errors that the user can't take meaningful action for.  Instead, we should log an error message and do the best we can.  (See discussion on CASSANDRA-7582.)

So, I've reverted this for now.  For the next attempt, we should

# Remember dropped cfids and avoid erroring out when replaying mutations matching those
# Add a "paranoid mode" (off by default) for deserialization errors, and enable it for tests


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