[
https://issues.apache.org/jira/browse/CASSANDRA-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203377#comment-17203377
]
Benedict Elliott Smith edited comment on CASSANDRA-14793 at 9/28/20, 5:08 PM:
------------------------------------------------------------------------------
Perhaps shut the server down for all writers and compaction, and serve only
reads? I've not got a strong opinion about it though - hard to run safely in
this context, so would seem fine to just admit defeat in this case. This does
strengthen the argument for replication system keyspace data to multiple disks
discussed above.
was (Author: benedict):
Perhaps shut the server down for all writers and compaction, and serve only
reads?
> 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: [email protected]
For additional commands, e-mail: [email protected]
