You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2015/08/24 17:37:45 UTC

[jira] [Updated] (CASSANDRA-10164) Re-apply MV updates on commitlog replay

     [ https://issues.apache.org/jira/browse/CASSANDRA-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani updated CASSANDRA-10164:
---------------------------------------
    Fix Version/s:     (was: 3.0 beta 2)
                   3.0.0 rc1

> Re-apply MV updates on commitlog replay
> ---------------------------------------
>
>                 Key: CASSANDRA-10164
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10164
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0.0 rc1
>
>
> If a node crashes between the Commit log update and local memtable update of the materialized view the node replica could lose MV data.  This is really only an issue for RF=1 since the other replicas will likely apply successfully.
> In any case we should fix this so MV updates are always applied even during commit log replay (with care to not re-add the mutations to the commit log).   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)