Re: Corrupted commit log prevents Cassandra start

If you already have a regular cadence of repair then you can set "commit_failure_policy" to ignore in cassandra.yaml. So that C* process does not crash on corrupt commit log. On Fri, Jul 7, 2017 at 2:10 AM, Hannu Kröger wrote: > Hello, > > yes, that’s what we do when things

Re: Corrupted commit log prevents Cassandra start

Hello, yes, that’s what we do when things like this happen. My thinking is just that when commit log is corrupted, you cannot really do anything else but exactly those steps. Delete corrupted file and run repair after starting. At least I haven’t heard of any tools for salvaging commit log

Re: Corrupted commit log prevents Cassandra start

Hi Hannu, I remember there have been discussions about this in the past. Most probably there is already a JIRA for this. I roughly remember a consense like that: - Default behaviour should remain - It should be configurable to the needs and preferences of the DBA - It should at least spit out