cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3456) Automatically create SHA1 of new sstables
Date Fri, 04 Nov 2011 20:13:51 GMT


Jonathan Ellis commented on CASSANDRA-3456:

I'm a little torn about adding another component -- leveled compaction will eat up fds really
quickly and adding more components will make that worse.  Putting it in the metadata/statistics
component is *almost* as user friendly (scrub can check it, or we can provide a standalone
sstablesha tool to extract it).  What do you think?
> Automatically create SHA1 of new sstables
> -----------------------------------------
>                 Key: CASSANDRA-3456
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
> Compressed sstables have block checksums which is great but non-compressed sstables don't
for technical/compatibility reasons that I'm not criticizing. It's a bit annoying because
when someone comes up with a corrupted file, we really have nothing to help discarding it
as bitrot or not. However, it would be fairly trivial/cheap to compute the SHA1 (or other)
of whole sstables when creating them. And if it's a new, separate, sstable component, we don't
even have to implement anything to check the hash. It would only be there to (manually) check
for bitrot when corruption is suspected by the user, or to say check the integrity of backups.
> I'm absolutely not pretending that it's a perfect solution, and for compressed sstables
the block checksums are clearly more fine grained, but it's easy to add and could prove useful
for non compressed files.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message