[
https://issues.apache.org/jira/browse/CASSANDRA-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642939#comment-14642939
]
Daniel Chia commented on CASSANDRA-9265:
----------------------------------------
[~aweisberg]
Two things:
First, it seems if we keep per record checksums in a separate checksum file,
then it may not be incredibly messy to skip checksumming if this file is
missing when running in backwards compatible mode.
Second, I was wondering if we could target 2.1 with this? I have seen quite a
few devs at my company run into corrupt saved caches on their development
boxes, and while as an operator it's pretty obvious to me to just wipe the
cache, it's not always clear to them that this is the cause of the error, and
that that's what they should do.
> Add checksum to saved cache files
> ---------------------------------
>
> Key: CASSANDRA-9265
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9265
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ariel Weisberg
> Fix For: 3.x
>
>
> Saved caches are not covered by a checksum. We should at least emit a
> checksum. My suggestion is a large checksum of the whole file (convenient
> offline validation), and then smaller per record checksums after each record
> is written (possibly a subset of the incrementally maintained larger
> checksum).
> I wouldn't go for anything fancy to try to recover from corruption since it
> is just a saved cache. If corruption is detected while reading I would just
> have it bail out. I would rather have less code to review and test in this
> instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
