[
https://issues.apache.org/jira/browse/CASSANDRA-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695438#comment-17695438
]
Runtian Liu commented on CASSANDRA-18294:
-----------------------------------------
I think this is the commit which breaks it:
[https://github.com/apache/cassandra/commit/db034609554a3185c0808cc67e9f0c148cc912c4]
Previously, there is no error handler call in
JVMStabilityInspector::inspectThrowable.
The above commit introduces the error handler before shutting down JVM. With
"die" disk failure policy, the error handler will throw exception so the jvm
shutdown code won't be reached.
> 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: [email protected]
For additional commands, e-mail: [email protected]
