cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-12956) CL is not replayed on custom 2i exception
Date Tue, 06 Dec 2016 11:11:29 GMT


Branimir Lambov updated CASSANDRA-12956:
    Status: Ready to Commit  (was: Patch Available)

> 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