cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13620) Don't skip corrupt sstables on startup
Date Wed, 05 Jul 2017 21:31:04 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075460#comment-16075460
] 

Ariel Weisberg commented on CASSANDRA-13620:
--------------------------------------------

Can you run the dtests on this just to make sure the change in logging and signatures doesn't
break any tests?

> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message