You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Runtian Liu (Jira)" <ji...@apache.org> on 2023/03/02 03:13:00 UTC
[jira] [Updated] (CASSANDRA-18294) die disk failure policy will not kill jvm as documented
[ https://issues.apache.org/jira/browse/CASSANDRA-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Runtian Liu updated CASSANDRA-18294:
------------------------------------
Bug Category: Parent values: Correctness(12982)
Complexity: Low Hanging Fruit
Discovered By: Code Inspection
> 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
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org