[
https://issues.apache.org/jira/browse/CASSANDRA-10130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007956#comment-16007956
]
Andrés de la Peña edited comment on CASSANDRA-10130 at 5/12/17 10:59 AM:
-------------------------------------------------------------------------
Good catch [~pauloricardomg]. We could make the
{{SecondaryIndexManager#markIndexRemoved}}/{{SecondaryIndexManager#markIndexBuilt}}
pair rely on these per index counters, and make sure that all index
rebuildings use them.
was (Author: adelapena):
Good catch [~pauloricardomg]. We could make the
{{SecondaryIndexManager#markIndexRemoved}}/{{SecondaryIndexManager#markIndexBuilt}}
rely on these per index counters, and make sure that all index rebuildings use
them.
> 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]
