You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Roth (JIRA)" <ji...@apache.org> on 2016/12/21 08:35:58 UTC
[jira] [Updated] (CASSANDRA-13065) Consistent range movements to
not require MV updates to go through write paths
[ https://issues.apache.org/jira/browse/CASSANDRA-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Roth updated CASSANDRA-13065:
--------------------------------------
Priority: Critical (was: Major)
> Consistent range movements to not require MV updates to go through write paths
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-13065
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13065
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Benjamin Roth
> Priority: Critical
>
> Booting or decommisioning nodes with MVs is unbearably slow as all streams go through the regular write paths. This causes read-before-writes for every mutation and during bootstrap it causes them to be sent to batchlog.
> The makes it virtually impossible to boot a new node in an acceptable amount of time.
> Using the regular streaming behaviour for consistent range movements works much better in this case and does not break the MV local consistency contract.
> Already tested on own cluster.
> Bootstrap case is super easy to handle, decommission case requires CASSANDRA-13064
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)