cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9308) Decouple streaming from secondary index rebuild
Date Tue, 05 May 2015 18:42:01 GMT

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

Brandon Williams commented on CASSANDRA-9308:
---------------------------------------------

One possible wrinkle to this though is that if the node is building an index and the source
dies, the source was also forwarding incoming writes to it so if the joining node continues
on like nothing happened when it jumps to normal it will actually be missing some data.

> Decouple streaming from secondary index rebuild
> -----------------------------------------------
>
>                 Key: CASSANDRA-9308
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9308
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: J.B. Langston
>
> Currently, streaming is not considered complete until any secondary indexes on the table
being streamed have been rebuilt.  If any source replicas go down after streaming completes,
but before the secondary indexes have been rebuilt, it will cause the bootstrap to fail, requiring
the user to go through the whole bootstrap process again. Ideally, the two should be decoupled
so that once the streaming is complete, the new node can complete the secondary index rebuild
and successfully boostrap regardless of the status of the source replicas at that point.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message