[
https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956104#comment-16956104
]
Marcus Eriksson commented on CASSANDRA-15332:
---------------------------------------------
bq. if a corrupt SSTable exception is thrown the disk failure policy does not
get applied
Looks like the reason for this is that we don't set the uncaught exception
handler in the in-jvm dtests - adding the same one as in `CassandraDaemon` in
`Instance#startup` makes us invoke the policy when there is a corrupt sstable
during validation.
> When building MerkleTrees if a CorruptSSTableException is thrown the
> DiskFailurePolicy does not get applied
> -----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15332
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15332
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a repair is in the validation phase and is building MerkleTrees, if a
> corrupt SSTable exception is thrown the disk failure policy does not get
> applied
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
