cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8498) Replaying commit log records that are older than gc_grace is dangerous
Date Wed, 17 Dec 2014 17:00:18 GMT

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

Benedict commented on CASSANDRA-8498:
-------------------------------------

In this situation a repair is a _really_ good idea, is all. Perhaps we should only fail if
there hasn't been a sufficiently new repair to have likely fixed any issue? Of course, I know
I have the strongest penchant for C* autodeath, but mostly because we know that users do not
read their log files as diligently as they should, and we get blamed if there are data corruption
or loss problems.

> 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
>          Components: Core
>            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