[
https://issues.apache.org/jira/browse/CASSANDRA-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630407#comment-16630407
]
Eric Evans commented on CASSANDRA-14793:
----------------------------------------
Awesome; I'd been meaning to open this very ticket.
I had planned to suggest what [~krummas] did, that it be possible to put
{{system}} in a different data directory. At least if this were possible,
{{system}} could be put on a RAID. And, at least in our environments, if the
expectation is that you can survive a single device failure, then the OS is
likely already on RAID-1 or similar.
Of course, if the tables in {{system}} could be regenerated, that would be
better still but I'm not sure what that looks like complexity-wise versus
pinning it.
> 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
> Reporter: Marcus Eriksson
> Priority: Major
> Fix For: 4.0
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
