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

Benjamin Roth edited comment on CASSANDRA-13065 at 3/2/17 12:06 PM:
--------------------------------------------------------------------

[~pauloricardomg] Please also look at follow-up commits on review. I added 2 
more commits (for 13064+13065) with tiny fixes. Depending on your feedback, I 
can rearrange them if required.

https://github.com/Jaumo/cassandra/tree/CASSANDRA-13064


was (Author: brstgt):
[~pauloricardomg] Please also look at follow-up commits on review. I added 2 
more commits (13064+13065) with tiny fixes. Depending on your feedback, I can 
rearrange them if required.

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

Reply via email to