cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13065) Consistent range movements to not require MV updates to go through write paths
Date Thu, 30 Mar 2017 19:55:41 GMT

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

Paulo Motta commented on CASSANDRA-13065:
-----------------------------------------

Thanks [~brstgt], this looks mostly good, except the following nits:
- Add header to {{StreamOperation}} test
- CDC should always go through write path on streaming, not only repair

After this can you squash and format your patch according to these [guidelines|https://cassandra.apache.org/doc/latest/development/patches.html#creating-a-patch]
(including CHANGES.txt entry).

I submitted CI tests for the current version of the patch:
||trunk||
|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-13065]|
|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-13065-testall/lastCompletedBuild/testReport/]|
|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-13065-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)

Mime
View raw message