[
https://issues.apache.org/jira/browse/CASSANDRA-18398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17716977#comment-17716977
]
Caleb Rackliffe commented on CASSANDRA-18398:
---------------------------------------------
[~blambov] A general question...as far as I can tell, the primary index SSTable
components historically have not, and still w/ this patch, do not, have any
kind of integrity checking/checksumming being performed on them, as opposed to
the data file, which is checked during streaming and new SSTable loading. (ex.
{{Walker}} doesn't look like it uses a checksumming {{Rebufferer}}.) This would
mean that they are susceptible to disk corruption, AFAICT. Have we thought
about whether that's an acceptable risk/performance trade-off?
CC [~dcapwell]
> CEP-25: Trie-indexed SSTable format
> -----------------------------------
>
> Key: CASSANDRA-18398
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18398
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/SSTable
> Reporter: Branimir Lambov
> Assignee: Branimir Lambov
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 15.5h
> Remaining Estimate: 0h
>
> Implementation of Big Trie-Indexed (BTI) SSTable format, per
> [CEP-25|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-25%3A+Trie-indexed+SSTable+format].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
