[
https://issues.apache.org/jira/browse/CASSANDRA-20363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933854#comment-17933854
]
Stefan Miklosovic commented on CASSANDRA-20363:
-----------------------------------------------
[CASSANDRA-20363|https://github.com/instaclustr/cassandra/tree/CASSANDRA-20363]
{noformat}
java17_pre-commit_tests
✓ j17_build 4m 36s
✓ j17_cqlsh_dtests_py311 7m 15s
✓ j17_cqlsh_dtests_py311_vnode 7m 38s
✓ j17_cqlsh_dtests_py38 7m 12s
✓ j17_cqlsh_dtests_py38_vnode 7m 24s
✓ j17_cqlshlib_cython_tests 8m 46s
✓ j17_cqlshlib_tests 10m 56s
✓ j17_dtests_latest 41m 6s
✓ j17_unit_tests 14m 43s
✓ j17_unit_tests_repeat 29m 22s
✓ j17_utests_latest 14m 58s
✓ j17_utests_latest_repeat 29m 21s
✓ j17_utests_oa 15m 57s
✓ j17_utests_oa_repeat 28m 0s
✕ j17_dtests 37m 48s
topology_test.TestTopology test_movement
refresh_test.TestRefresh test_refresh_deadlock_startup
✕ j17_dtests_vnode 43m 34s
materialized_views_test.TestMaterializedViews
test_complex_mv_select_statements
✕ j17_jvm_dtests 26m 30s
org.apache.cassandra.fuzz.sai.MultiNodeSAITest indexOnlySaiTest TIMEOUTED
✕ j17_jvm_dtests_latest_vnode 26m 13s
org.apache.cassandra.fuzz.sai.MultiNodeSAITest indexOnlySaiTest TIMEOUTED
{noformat}
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/5556/workflows/d255f649-e6ec-4fef-a738-49d1f0483f84]
> 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: [email protected]
For additional commands, e-mail: [email protected]
