[
https://issues.apache.org/jira/browse/CASSANDRA-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-13620:
----------------------------------------
Assignee: Marcus Eriksson
Fix Version/s: 4.x
3.11.x
3.0.x
Status: Patch Available (was: Open)
Patch to catch IOExceptions and rethrow them as CorruptSSTableExceptions - if
we get an IOException when opening an sstable, it should be considered corrupt
https://github.com/krummas/cassandra/commits/marcuse/13620
https://github.com/krummas/cassandra/commits/marcuse/13620-3.11
https://github.com/krummas/cassandra/commits/marcuse/13620-trunk
The trunk version removes the {{throws IOException}} from all open* methods, I
kept it in the earlier versions as I guess it can be considered a public API
> Don't skip corrupt sstables on startup
> --------------------------------------
>
> Key: CASSANDRA-13620
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13620
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> If we get an IOException when opening an sstable on startup, we just
> [skip|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/SSTableReader.java#L563-L567]
> it and continue starting
> we should use the DiskFailurePolicy and never explicitly catch an IOException
> here
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
