cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8498) Replaying commit log records that are older than gc_grace is dangerous
Date Fri, 27 May 2016 16:20:12 GMT

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

Joshua McKenzie commented on CASSANDRA-8498:
--------------------------------------------

bq.  We advise operators not to do this (in order to avoid zombie data), but there are cases
where it makes sense
If the assumed majority case is "don't do this unless you really know what you're doing",
I think we should reflect that in our operations. I'm +1 on failing to start w/out a specific
flag that you know what you're doing, and having a relatively verbose log message on failed
startup w/out that flag.

> Replaying commit log records that are older than gc_grace is dangerous
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-8498
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8498
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Benedict
>
> If we replay commit log records that are older than gc_grace we could introduce data
corruption to the cluster. We should either (1) fail and suggest a repair, or (2) log an exception.
I prefer (1).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message