[
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902297#comment-17902297
]
Stefan Miklosovic commented on CASSANDRA-11695:
-----------------------------------------------
I've cherry-picked [~samt]'s "hack" around java.security.auth.login.config too.
We have two ways to configure this. The legacy way via cassandra-env.sh and the
yaml way. Both configured will throw exception. If we want to configure it via
yaml. All it takes is to comment out one function call in cassandra-env.sh
(configure_jmx) and no system properties will be set whatsover and all will be
taken from yaml. If we want to keep it configured via cassandra-env.sh, then a
user does not need to do anything.
> Move JMX connection config to cassandra.yaml
> --------------------------------------------
>
> Key: CASSANDRA-11695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11695
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Sam Tunnicliffe
> Assignee: Stefan Miklosovic
> Priority: Low
> Labels: lhf
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Since CASSANDRA-10091, we always construct the JMX connector server
> programatically, so we could move its configuration from cassandra-env to
> yaml.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
