[jira] [Commented] (CASSANDRA-13065) Consistent range movements to not require MV updates to go through write paths

["Benjamin Roth (JIRA)" <ji...@apache.org>]

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

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

[~pauloricardomg]

There you go. My first complete patch. I hope its ok and works :)
https://github.com/Jaumo/cassandra/commit/88699700feb6b9a504df88ff063b82641d7939f7

> 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
>            Assignee: Benjamin Roth
>            Priority: Critical
>             Fix For: 4.0
>
>
> 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.15#6346)