[
https://issues.apache.org/jira/browse/CASSANDRA-16879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404737#comment-17404737
]
Caleb Rackliffe commented on CASSANDRA-16879:
---------------------------------------------
Very minor note...I think we have typically included all authors WRT the
{{Co-authored-by}} tag. In this case, I think that would mean both you and Sam
are tagged. (I can see how you could go that way with it, of course, if the
main author tag already pointed to Sam. Not a huge deal either way I guess,
unless we had some reporting/analytics that assumed "primary" authors are also
technically co-authors...)
> Verify correct ownership of attached locations on disk at C* startup
> --------------------------------------------------------------------
>
> Key: CASSANDRA-16879
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16879
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.x
>
>
> There's two primary things related to startup and disk ownership we should
> mitigate.
> First, an instance can come up with an incorrectly mounted volume attached as
> its configured data directory. This causes the wrong system tables to be
> read. If the instance which was previously using the volume is also down, its
> token could be taken over by the instance coming up.
> Secondly, in a JBOD setup, the non-system keyspaces may reside on a separate
> volume to the system tables. In this scenario, we need to ensure that all
> directories belong to the same instance, and that as the instance starts up
> it can access all the directories it expects to be able to. (including data,
> commit log, hints and saved cache dirs)
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
