[
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17822224#comment-17822224
]
Stefan Miklosovic commented on CASSANDRA-11695:
-----------------------------------------------
I will try to resurrect this ticket, it is 7.5 years from the last discussion /
feedback. I will assign this to myself, if [~zzheng] protests suddenly, please
feel free to take it from me.
There is also CASSANDRA-18508 which came up with a similar idea so I think we
might somehow merge one patch with the other and hash out the discrepancies
which were introduced over all these years.
Let's see how far we get!
> 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]
