cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-10130) Node failure during 2i update after streaming can have incomplete 2i when restarted
Date Tue, 06 Jun 2017 05:05:18 GMT

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

Paulo Motta edited comment on CASSANDRA-10130 at 6/6/17 5:05 AM:
-----------------------------------------------------------------

Sorry for being picky here but while we are fixing the original limitation, we are introducing
a new limitation that if there's ever a non-fatal index build failure, a successful full index
rebuild will not mark the index as built until the node is restarted and the index is unnecessarily
rebuilt.

We can probably lift this limitation fairly simply by marking the index as built (and clear
the pending counters) if there was no other index build submission since the start of the
full rebuild - even if there are (likely failed) pending builds. We also should probably log
a warning when there is an index build failure instructing the user to run a full index rebuild
to fix it.


was (Author: pauloricardomg):
Sorry for being picky here but while we are fixing the original limitation, we are introducing
a new limitation that if there's ever a non-fatal index build failure, a successful full index
rebuild will not mark the index as built until the node is restarted and the index is unnecessarily
rebuilt.

We can probably lift this limitation fairly simply by marking the index as built (and clear
the pending counters) if there was no other index build submission since the start of the
full rebuild - even if there are (likely failed) pending builds. We should probably log a
warning when there is an index build failure instructing the user to run a full index rebuild
to fix it.

> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message