cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-9749) CommitLogReplayer continues startup after encountering errors
Date Tue, 07 Jul 2015 17:21:05 GMT
Blake Eggleston created CASSANDRA-9749:
------------------------------------------

             Summary: CommitLogReplayer continues startup after encountering errors
                 Key: CASSANDRA-9749
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9749
             Project: Cassandra
          Issue Type: Bug
            Reporter: Blake Eggleston
             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: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java#L298

Or if there are compressor problems here: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java#L314
and here: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java#L366

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
(v6.3.4#6332)

Mime
View raw message