[
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709298#comment-14709298
]
Benedict commented on CASSANDRA-10130:
--------------------------------------
The latter. Unless there were disk corruption of the transaction log detected,
in which case it is pessimistic and assumes they should be kept. We could
change this behaviour for MVs, and default to deletion instead.
> Node failure during MV/2i update after streaming can have incomplete MV/2i
> when restarted
> -----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10130
> Project: Cassandra
> Issue Type: Bug
> Reporter: Yuki Morishita
> Assignee: Carl Yeksigian
> Priority: Minor
> Fix For: 3.0.0 rc1
>
>
> 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.4#6332)
