[
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724168#comment-17724168
]
Stefan Miklosovic edited comment on CASSANDRA-11695 at 5/19/23 7:42 AM:
------------------------------------------------------------------------
I believe this is being worked on in CASSANDRA-18508.
FYI [~Anthony Grasso].
We could reuse the work in the patches in this ticket and cherry-pick what is
needed or we may continue in this one and finish it. Up to you.
was (Author: smiklosovic):
I believe this is being worked on in CASSANDRA-18508.
FYI [~Anthony Grasso].
> Move JMX connection config to cassandra.yaml
> --------------------------------------------
>
> Key: CASSANDRA-11695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11695
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Sam Tunnicliffe
> Assignee: Zhongxiang Zheng
> Priority: Low
> Labels: lhf
> Fix For: 3.11.x
>
>
> 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]
