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

Chris Lohfink commented on CASSANDRA-11695:
-------------------------------------------

This is a great change, always nervous about these breaking tooling and peoples 
environments but being just on trunk I think makes that risk not really an 
issue imho

> 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: 5h
>  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]

Reply via email to