You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2020/09/28 15:43:00 UTC
[jira] [Commented] (CASSANDRA-14793) Improve system table handling
when losing a disk when using JBOD
[ https://issues.apache.org/jira/browse/CASSANDRA-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203307#comment-17203307 ]
Benjamin Lerer commented on CASSANDRA-14793:
--------------------------------------------
[~marcuse], [~benedict] How do you think we should handle the case where the {{disk_failure_policy}} is {{best_effort}} and the disk containing the system data is marked as {{unreadable}} or {{unwritable}} ?
> Improve system table handling when losing a disk when using JBOD
> ----------------------------------------------------------------
>
> Key: CASSANDRA-14793
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14793
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Marcus Eriksson
> Assignee: Benjamin Lerer
> Priority: Normal
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We should improve the way we handle disk failures when losing a disk in a JBOD setup
> One way could be to pin the system tables to a special data directory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org