cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9749) CommitLogReplayer continues startup after encountering errors
Date Tue, 11 Aug 2015 21:57:46 GMT


Ariel Weisberg commented on CASSANDRA-9749:

Boolean.getBoolean() can check the system property

What is the motivation for changing this to warn? Is it going to cause operators concern that
is unwarranted?

Do you have to make all those object arrays for handleReplayError? varargs won't handle it

The changes look reasonable. Some of the error conditions that now are supposed to throw don't
have unit test coverage. They weren't tested before either, but this an opportunity to make
sure the errors work.

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