[jira] [Commented] (CASSANDRA-10130) Node failure during MV/2i update after streaming can have incomplete MV/2i when restarted

["T Jake Luciani (JIRA)" <ji...@apache.org>]

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

T Jake Luciani commented on CASSANDRA-10130:
--------------------------------------------

[~yukim] I don't think this is an issue.  We have a transaction for the StreamingFileTask that only succeeds if all the mutations were applied.  If the node dies during then the sstable isn't marked finished AFAIK.  

[~benedict] If the transaction doesn't succeed would the sstables be used or cleaned up on restart? I would expect the latter.

> 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)