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] [Commented] (CASSANDRA-10061) Only use batchlog when paired view replica is remote
Date Mon, 24 Aug 2015 13:24:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709275#comment-14709275
] 

T Jake Luciani commented on CASSANDRA-10061:
--------------------------------------------

bq. What happens if a node dies between the apply() calls? We'll still recover all right?

This is an issue with the current implementation as well (crash after commit log update but
before MV batchlog is applied).

I've created CASSANDRA-10164 to fix.

> Only use batchlog when paired view replica is remote
> ----------------------------------------------------
>
>                 Key: CASSANDRA-10061
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10061
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0 beta 2
>
>
> As described in the MV design doc the base and view replicas are paired one to one.
> If the replica selected for the view is the local node itself there is no need to create
a local batchlog and we can simply apply the view mutations locally.



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

Mime
View raw message