Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 3 Oct 2012 00:53:07 +1100 (NCT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <928054165.154301.1349185987977.JavaMail.jiratomcat@arcas>
In-Reply-To: <177566156.136884.1348790227988.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CASSANDRA-4730) CommitLogReplayer should report
 the bad CRC checksum in the log
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-4730:
-------------------------------------------

Use batch commitlog mode if you want to be sure not to lose data on unclean shutdown.  Do clean shutdowns with periodic mode if you want the same.
                
> CommitLogReplayer should report the bad CRC checksum in the log
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-4730
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4730
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.5
>         Environment: Cassandra 1.1.5
>            Reporter: Arya Goudarzi
>
> If commit log isn't fully fsynced, the record which fails the checksum is not replayed do this logic. It would be beneficial to log that as an error so that user can know easily what happened.
> "./src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java" line 188 of 287 --65%-- col 54

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira