[CASSANDRA-16879] Verify correct ownership of attached locations on disk at C* startup

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.1-alpha1, 4.1
• Component/s: Local/Startup and Shutdown
• Change Category: Operability
• Complexity: Normal
• Platform: All

Source Control Link

https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=2e2db4dc40c4935305b9a2d5d271580e96dabe42

Test and Documentation Plan

New testing. Will need to document this on the official docs page based on javadocs in classes.

• Assignee: Josh McKenzie Assign to me
• Reporter: Josh McKenzie

Authors

Josh McKenzie

Reviewers

Caleb Rackliffe

• Created: 24/Aug/21 15:39
• Updated: 27/May/22 19:25
• Resolved: 05/Oct/21 16:15

Description

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)