cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Petrov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-12956) CL is not replayed on custom 2i exception
Date Mon, 05 Dec 2016 15:57:58 GMT


Alex Petrov commented on CASSANDRA-12956:

Great, thank you.
I've removed the duplicate {{await}}, thanks for catching that. {{truncate}} check for {{false}}
is done in [flush memtable|].

I've applied the change to all branches and did CI.

> CL is not replayed on custom 2i exception
> -----------------------------------------
>                 Key: CASSANDRA-12956
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alex Petrov
>            Assignee: Alex Petrov
>            Priority: Critical
> If during the node shutdown / drain the custom (non-cf) 2i throws an exception, CommitLog
will get correctly preserved (segments won't get discarded because segment tracking is correct).

> However, when it gets replayed on node startup,  we're making a decision whether or not
to replay the commit log. CL segment starts getting replayed, since there are non-discarded
segments and during this process we're checking whether there every [individual mutation|]
in commit log is already committed or no. Information about the sstables is taken from [live
sstables on disk|].

This message was sent by Atlassian JIRA

View raw message