[
https://issues.apache.org/jira/browse/CASSANDRA-16879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405445#comment-17405445
]
Michael Semb Wever commented on CASSANDRA-16879:
------------------------------------------------
Yup, this is totally tribal knowledge. It has been (3), and (2) has been added
along the way. One can presume (1) is a author or reviewer, but that ends up
being superfluous information.
Discovered when implementing https://github.com/apache/cassandra-builds/pull/54
See
https://github.com/apache/cassandra-builds/pull/54/files?file-filters%5B%5D=.groovy&file-filters%5B%5D=.py&file-filters%5B%5D=.sh#diff-5395e918664bf9171112efaf9ccba62a3bf85edef47fe86c93e7ba7e5455aac8R452-R512
Clear as mud?
> 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]
