[CASSANDRA-17220] Make startup checks configurable

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

Source Control Link

https://github.com/apache/cassandra/commit/eac9d925621dc1757ac88ac7160dc0b2bd3e0015

Test and Documentation Plan

unit tests

• Assignee: Stefan Miklosovic
• Reporter: Stefan Miklosovic

Authors

Stefan Miklosovic

Reviewers

Paulo Motta

• Created: 18/Dec/21 09:37
• Updated: 27/May/22 19:25
• Resolved: 27/Feb/22 23:44

Description

This ticket was created from needs discovered in CASSANDRA-17180. We want to be able to configure a startup check so we figured out that it is necessary to treat all startup checks same - to be able to configure them. This ticket is about making startup checks configurable.

Once this ticket is done, we can continue with the implementation of CASSANDRA-17180 where the implementation of gc grace check will be done.

We have identified that there is one check currently in place which needs to be changed to reflect this configuration implementation and that is FileSystemOwnershipCheck.

Because startup checks were not configurable before via means of a configuration file, they were configurable via system properties. This ticket does not aim to get rid system properties configuration mechanism, system properties will have precedence over settings in configuration file. Then, in the next release, I am aiming to get rid of system properties configuration mechanism.

Issue Links

• blocks: CASSANDRA-17180 Implement startup check to prevent Cassandra start to spread zombie data
• is related to: CASSANDRA-17292 Move cassandra.yaml toward a nested structure around major database concepts