[
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007507#comment-16007507
]
Paulo Motta commented on CASSANDRA-10130:
-----------------------------------------
Good call [~sbtourist]! I thought setting the index removed would make the
queries unavailable so I haven't considered this route, my bad!
There is still a slight possibility of race though if an index is being built
by some other thread and we mark the index as built after the streaming
operation but before the other thread build is completed.
Perhaps we could have a counter incremented each time an index starts
rebuilding and only call {{markIndexBuilt}} if this counter is zero when the
index finishes rebuilding?
Dtest looks good!
> Node failure during 2i update after streaming can have incomplete 2i when
> restarted
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
> Issue Type: Bug
> Components: Coordination
> Reporter: Yuki Morishita
> Assignee: Andrés de la Peña
> Priority: Minor
>
> Since MV/2i update happens after SSTables are received, node failure during
> MV/2i update can leave received SSTables live when restarted while MV/2i are
> partially up to date.
> We can add some kind of tracking mechanism to automatically rebuild at the
> startup, or at least warn user when the node restarts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
