[
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17902517#comment-17902517
]
Maulin Vasavada commented on CASSANDRA-11695:
---------------------------------------------
Okay Stefan, I reviewed the latest changes and we are in alignment - regarding
# Keeping `LOCAL_JMX` outside of the `configure_jmx()` method in the
`cassandra-env.sh`
# Keeping ability to define `jmx_port` in the `jmx_server_options`
# Throwing configuration error when we detect JMX configured via the system
property & cassandra yamlÂ
Left further minor comments on the PR.
> 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: 2h 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]
