cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Roth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13065) Consistent range movements to not require MV updates to go through write paths
Date Wed, 21 Dec 2016 08:35:58 GMT

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

Benjamin Roth commented on CASSANDRA-13065:
-------------------------------------------

I marked it as critical as it severly affects cluster maintainability when using MVs. Maybe
it's also worth to be considered as a bug.

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

Mime
View raw message