[
https://issues.apache.org/jira/browse/CASSANDRA-14793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630172#comment-16630172
]
Kurt Greaves commented on CASSANDRA-14793:
------------------------------------------
IDK that pinning the system tables really fixes the issue as we'll still have
the problem of losing one disk means a whole node replacement.
Theoretically it should be possible to rebuild the (important) system tables in
the case they get corrupted. Most things currently should be able to be
retrieved from gossip/other nodes. How about if there's something we currently
can't retrieve we just store it in the peers table on all the nodes. I can't
imagine the amount of info we'd have to store would be very big. Then we can
just provide a startup flag to indicate that a node should try and rebuild its
system tables.
> 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: [email protected]
For additional commands, e-mail: [email protected]
