[
https://issues.apache.org/jira/browse/CASSANDRA-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905449#comment-15905449
]
Jason Brown commented on CASSANDRA-13321:
-----------------------------------------
[~krummas] elaborate a little further in an offline conversation:
{quote}
a problem is when we change the repairedAt in an existing file for example,
some other thread could want to deserialize the compaction metadata (which is
in the same file) and fail because the file changed while it was deserializing,
if we safely instead add a new file we will avoid that
{quote}
I agree with this idea, and I'll leave it to Marcus to make the magic happen.
> Add a checksum component for the sstable metadata (-Statistics.db) file
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-13321
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13321
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 4.x
>
>
> Since we keep important information in the sstable metadata file now, we
> should add a checksum component for it. One danger being if a bit gets
> flipped in repairedAt we could consider the sstable repaired when it is not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
