[
https://issues.apache.org/jira/browse/CASSANDRA-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697494#comment-17697494
]
Stefan Miklosovic commented on CASSANDRA-18294:
-----------------------------------------------
[~brandon.williams] as [~maxwellguo] mentioned here (1) it seems we are OK
already?
added "die" is there so we would not throw IllegalStateException as it would
reach "default" in these switches which this ticket solves.
(1) https://github.com/apache/cassandra/pull/2189/files#r1122779198
> die disk failure policy will not kill jvm as documented
> -------------------------------------------------------
>
> Key: CASSANDRA-18294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18294
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Runtian Liu
> Assignee: Runtian Liu
> Priority: Normal
> Fix For: 3.0.x, 4.0.x, 4.1.x
>
>
> After Cassandra has successfully starts up with disk_failure_policy die, when
> encounter a file system error, Cassandra server will only throw exception
> instead of shut down gossip and client transport and kill JVM. Document:
> [https://cassandra.apache.org/doc/latest/cassandra/configuration/cass_yaml_file.html#disk_failure_policy]
>
> The reason for this is the default FS error handler is not handing policy die
> correctly. Instead of shutting down gossip and native transport, it throws an
> error.
>
> The JVMStabilityInspectorTest is passing because the error handler is not set
> so no exception is thrown.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
