You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2025/03/04 09:04:00 UTC

[jira] [Updated] (CASSANDRA-20363) Introduce a robust way to intercept FSError and commit log errors

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

Stefan Miklosovic updated CASSANDRA-20363:
------------------------------------------
    Status: Needs Committer  (was: Patch Available)

> Introduce a robust way to intercept FSError and commit log errors
> -----------------------------------------------------------------
>
>                 Key: CASSANDRA-20363
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20363
>             Project: Apache Cassandra
>          Issue Type: New Feature
>          Components: Legacy/Core
>            Reporter: Tommy Stendahl
>            Assignee: Tommy Stendahl
>            Priority: Normal
>             Fix For: 5.x
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Add java property to override the DefaultFSErrorHandler with a custom implementation.
> The use case I am looking at is a customer deployment that are using network disks and these can go off-line sometimes, I would like to use "disk_failure_policy: stop" but automatically detect when the disk is on-line again and just open gossip and transports so the nodes comes back UP without triggering a restart of the node.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org