cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10164) Re-apply MV updates on commitlog replay
Date Thu, 27 Aug 2015 16:09:45 GMT

     [ 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.0 rc1)
                   3.0 beta 2

> 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 beta 2
>
>
> 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)

Mime
View raw message