[
https://issues.apache.org/jira/browse/CASSANDRA-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959002#comment-15959002
]
Paulo Motta commented on CASSANDRA-13065:
-----------------------------------------
Thanks, when I was about to commit I noticed that this will change the behavior
of bulk loading (sstableloader) of base tables: before we rebuilt the views
when base tables were bulk loaded but right now the user will either need to
manually load the view sstables or trigger a manual view rebuild.
While we can provide this as a bulk loader option in the future, we should keep
the behavior for bulk loading since this potentially inserts new data into the
cluster, so I did a minor change to the patch to also not skip the write path
for bulk loading and others (since the behavior is undefined in this case) -
[~brstgt] can you double check this minor change, the core of the change is
[this
line|https://github.com/pauloricardomg/cassandra/commit/1344f9ba7b620d31c07487973c6545514ef40476#diff-1a464da4a62ac4a734c725059cbc918bR161].
I also updated the ticket description to {{Skip building views during base
table streams on range movements}} to better reflect what was done here.
This is nearly there, hopefully the final round of CI:
||trunk||
|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-13064]|
|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-13064-testall/lastCompletedBuild/testReport/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-13064-dtest/lastCompletedBuild/testReport/]|
> 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)
