[jira] [Updated] (CASSANDRA-13620) Don't skip corrupt sstables on startup

["Marcus Eriksson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Eriksson updated CASSANDRA-13620:
----------------------------------------
    Attachment: 13620-trunk.png
                13620-3.0.png
                13620-3.11.png

3.0:
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/210/testReport/
[^13620-3.0.png]

3.11:
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/208/testReport/
[^13620-3.11.png]

trunk:
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/207/testReport/
[^13620-trunk.png]

trying to figure out if any of the failures are caused by this patch

> 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
>
>         Attachments: 13620-3.0.png, 13620-3.11.png, 13620-trunk.png
>
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org