[
https://issues.apache.org/jira/browse/CASSANDRA-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18294:
-----------------------------------------
Fix Version/s: 3.0.29
4.0.9
4.1.1
5.0
(was: 3.0.x)
(was: 4.0.x)
(was: 4.1.x)
Since Version: 3.0.28
Source Control Link:
https://github.com/apache/cassandra/commit/be574fc34ba9834929f1618ab63dd74446cd2683
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed, thanks everyone!
> 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.29, 4.0.9, 4.1.1, 5.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
