cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9749) CommitLogReplayer continues startup after encountering errors
Date Mon, 17 Aug 2015 16:47:46 GMT


Benedict commented on CASSANDRA-9749:

I cannot find where the conversation happened, so perhaps it was on IRC, but the consensus
had shifted since we last discussed this over a year ago. There was wide support for failing
on startup if the commit log is corrupted, and printing an error message for the user to opt
into continuing in the face of those errors. iirc, [~aweisberg], [~bdeggleston] and [~jjordan]
were participants, amongst others, so perhaps they can corroborate this since I cannot find
a reference.

> CommitLogReplayer continues startup after encountering errors
> -------------------------------------------------------------
>                 Key: CASSANDRA-9749
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Blake Eggleston
>            Assignee: Branimir Lambov
>             Fix For: 2.2.x
>         Attachments: 9749-coverage.tgz
> There are a few places where the commit log recovery method either skips sections or
just returns when it encounters errors.
> Specifically if it can't read the header here:
> Or if there are compressor problems here:
and here:
> Whether these are user-fixable or not, I think we should require more direct user intervention
(ie: fix what's wrong, or remove the bad file and restart) since we're basically losing data.

This message was sent by Atlassian JIRA

View raw message