[ 
https://issues.apache.org/jira/browse/CASSANDRA-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18051519#comment-18051519
 ] 

Stefan Miklosovic edited comment on CASSANDRA-21093 at 1/13/26 1:43 PM:
------------------------------------------------------------------------

thanks [~nickbar01234] for taking a look

reworked patch here https://github.com/apache/cassandra/pull/4557/files

[~mck] do you want to take a look? Still need another review ... 


was (Author: smiklosovic):
reworked patch here https://github.com/apache/cassandra/pull/4557/files

[~mck] do you want to take a look? Still need another review ... 

> Custom startup checks plugin
> ----------------------------
>
>                 Key: CASSANDRA-21093
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21093
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Legacy/Core
>            Reporter: Nick Doan
>            Assignee: Nick Doan
>            Priority: Normal
>             Fix For: 5.x
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> {{Currently, the list of available startup checks is fixed for a given 
> distribution. Users can optionally override whether a check type is executed 
> using {_}startup_checks{_}.}}
>  
> In some deployment environments, users may want to have additional checks in 
> place, but currently, this would require running these checks separately 
> before launching the Cassandra daemon. Can we potentially add support for 
> {_}custom_startup_checks{_}, which takes a list of classes to be dynamically 
> loaded at runtime from classpath? Alternatively, if custom deployments wraps 
> CassandraDaemon, we can also consider exposing startup checks as a public 
> singleton so that the wrapper can register additional startup checks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to