[
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029960#comment-16029960
]
Caleb Rackliffe commented on CASSANDRA-10130:
---------------------------------------------
bq. We could either add a new field to SSTableAddedNotification to indicate
wether the added sstables come from flush or external sstables or create two
new notifications which would inherit from SSTableAddedNotification to maintain
backward compatibility, perhaps: SSTableFlushedNotification and
ExternalSSTableLoadedNotification.
The {{SSTableFlushedNotification}} approach sounds cleaner, mostly because it
could carry an unambiguously non-null reference to the flushed {{Memtable}}.
> 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: [email protected]
For additional commands, e-mail: [email protected]
