[
https://issues.apache.org/jira/browse/CASSANDRA-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Doan updated CASSANDRA-21093:
----------------------------------
Description:
{{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.
was:
{{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.
> Custom startup checks plugin
> ----------------------------
>
> Key: CASSANDRA-21093
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21093
> Project: Apache Cassandra
> Issue Type: Improvement
> Reporter: Nick Doan
> Priority: Normal
>
> {{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]
