cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-9749) CommitLogReplayer continues startup after encountering errors
Date Fri, 14 Aug 2015 18:34:46 GMT


Ariel Weisberg updated CASSANDRA-9749:
    Attachment: 9749-coverage.tgz

Do I need to run the tests with specific settings to hit a compression path? I ran the tests
and merged the results and it didn't make it all the way in.

I attached the HTML coverage report I get. I don't have a better way to do this yet.

Looking at the tests, it seems like they don't actually run. Some are missing the @Test annotation.

> 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