[
https://issues.apache.org/jira/browse/CASSANDRA-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-15143:
-------------------------------------------
Fix Version/s: (was: 4.x)
4.0-alpha
Since Version: 2.2.0 beta 1
Source Control Link:
https://github.com/apache/cassandra/commit/e597d48bda845815dada7cf53f705ae273d8f457
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed as e597d48bda845815dada7cf53f705ae273d8f457
> Remove assertion on file deletion to trigger failure policy
> -----------------------------------------------------------
>
> Key: CASSANDRA-15143
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15143
> Project: Cassandra
> Issue Type: Bug
> Components: Local/SSTable
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> Deleting any files by using FileUtils.deleteWithConfirm() will involve
> checking for file existence using an assertion. If the assertion passes, any
> errors from the actual Files.delete() operation will get handled as a
> FSWriteError and invoke the DiskFailurePolicy. This will get us to a
> situation where only some cases of bad FS or disk issues will be handed by
> the DFP, while FS issues that may already cause the file.exists() assertion
> to fail, will only manifest as AssertionErrors. We should invoke DFP for the
> later as well and remove the assertion altogether.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
