[ https://issues.apache.org/jira/browse/CASSANDRA-13065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932912#comment-15932912 ]
Joshua McKenzie commented on CASSANDRA-13065: --------------------------------------------- It looks like we can always just use {{appendToCommitLog}} for CDC-enabled cfs + the standard streaming code rather than using the write path the way MV's do. CDC has no requirement for the data to make it back into a memtable or to go through the entire write path; what we really need is to ensure that data makes it to the CL and the segments get flagged as containing CDC-enabled cf's which this code should do. > 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)