[
https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959982#comment-16959982
]
David Capwell commented on CASSANDRA-15332:
-------------------------------------------
Found out that my change only got execute to work, and that submit had the same
behavior with and without tracing (that the exception is lost).
I rewrote my patch to make sure execute and submit methods matches the behavior
of normal ExecutorService calls, but did not loose the underline exception.
I also added documentation to help explain how this works, though its rather
ugly so the documentation may not be enough.
Let me know what you think.
> When repair is running with tracing, if a CorruptSSTableException is thrown
> while building Merkle Trees 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, Observability/Tracing
> 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: [email protected]
For additional commands, e-mail: [email protected]
