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

David Capwell updated CASSANDRA-15332:
--------------------------------------
    Test and Documentation Plan: 
||branch||diff||tests||
|[branch|https://github.com/dcapwell/cassandra/tree/repairCorruption]|[diff|https://github.com/apache/cassandra/compare/trunk...dcapwell:repairCorruption]|[tests|https://circleci.com/gh/dcapwell/workflows/cassandra/tree/repairCorruption]|



Changes:

1) JVMStabilityInspector checks for corruption or FSError and delegates to 
FileUtils for handling

2) FileUtils now implements the die behavior

3) JVMStabilityInspector now walks suppressed exceptions as well as the caused 
exception (edge case not in streaming where the second exception is fserror or 
corruption, so just added since saw suppression was common)

4) dtest updated to keep track of the number of kill attempts (though does not 
kill, mostly so tests can reuse the cluster)

Test case added which causes a corruption exception to be thrown from a SSTable 
during validation and shows that the handling makes its way to JVMStabilities 
kill instance method.

  was:
||branch||diff||tests||
|[branch|https://github.com/dcapwell/cassandra/tree/repairCorruption]|[diff|https://github.com/apache/cassandra/compare/trunk...dcapwell:repairCorruption]|[tests|https://circleci.com/workflow-run/760a2f16-1084-4cf4-b789-008c7e325602]|



Changes:

1) JVMStabilityInspector checks for corruption or FSError and delegates to 
FileUtils for handling

2) FileUtils now implements the die behavior

3) JVMStabilityInspector now walks suppressed exceptions as well as the caused 
exception (edge case not in streaming where the second exception is fserror or 
corruption, so just added since saw suppression was common)

4) dtest updated to keep track of the number of kill attempts (though does not 
kill, mostly so tests can reuse the cluster)

Test case added which causes a corruption exception to be thrown from a SSTable 
during validation and shows that the handling makes its way to JVMStabilities 
kill instance method.


> 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
>             Fix For: 4.0
>
>
> 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]

Reply via email to