You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "ZhaoYang (JIRA)" <ji...@apache.org> on 2017/07/11 08:27:00 UTC

[jira] [Commented] (CASSANDRA-10654) Make MV streaming rebuild parallel

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

ZhaoYang commented on CASSANDRA-10654:
--------------------------------------

Is this issue still valid after CASSANDRA-13065 is merged? now when bootstrapping,  the base data will not go through write-path..

> Make MV streaming rebuild parallel
> ----------------------------------
>
>                 Key: CASSANDRA-10654
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10654
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>             Fix For: 4.x
>
>
> When streaming a sstable that is a base table for one or more materialized views we force the data through the mutation path to ensure the MVs are updated.
> We currently do this sequentially so it's a bottleneck.  We should do this in parallel.  We want to be smart to not saturate the mutations in the non-bootstrap case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org