Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 1 Mar 2017 11:09:45 +0000 (UTC)
From: "Benjamin Roth (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13029668.1482309820000.29369.1488366585388@Atlassian.JIRA>
In-Reply-To: <JIRA.13029668.1482309820000@Atlassian.JIRA>
References: <JIRA.13029668.1482309820000@Atlassian.JIRA> <JIRA.13029668.1482309820878@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CASSANDRA-13066) Fast streaming with materialized
 views
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 01 Mar 2017 11:09:50 -0000


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

Benjamin Roth updated CASSANDRA-13066:
--------------------------------------
    Summary: Fast streaming with materialized views  (was: Fast repair with materialized views)

> Fast streaming with materialized views
> --------------------------------------
>
>                 Key: CASSANDRA-13066
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13066
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benjamin Roth
>
> I propose adding a configuration option to send streams of tables with MVs not through the regular write path.
> This may be either a global option or better a CF option.
> Background:
> A repair of a CF with an MV that is much out of sync creates many streams. These streams all go through the regular write path to assert local consistency of the MV. This again causes a read before write for every single mutation which again puts a lot of pressure on the node - much more than simply streaming the SSTable down.
> In some cases this can be avoided. Instead of only repairing the base table, all base + mv tables would have to be repaired. But this can break eventual consistency between base table and MV. The proposed behaviour is always safe, when having append-only MVs. It also works when using CL_QUORUM writes but it cannot be absolutely guaranteed, that a quorum write is applied atomically, so this can also lead to inconsistencies, if a quorum write is started but one node dies in the middle of a request.
> So, this proposal can help a lot in some situations but also can break consistency in others. That's why it should be left upon the operator if that behaviour is appropriate for individual use cases.
> This issue came up here:
> https://issues.apache.org/jira/browse/CASSANDRA-12888?focusedCommentId=15736599&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15736599


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)