[
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365807#comment-15365807
]
Zhongxiang Zheng commented on CASSANDRA-11695:
----------------------------------------------
Almost all JMX settings except keystore and truststore settings are moved to
yaml in below commit.
https://github.com/zx-zheng/cassandra/commit/70b176e2ae401e86e1d703d3583a909c0ceb5176
The branch is below.
https://github.com/zx-zheng/cassandra/tree/11695
If JMX options are set in both cassandra-env and yaml, settings in
cassandra-env are taken precedence.
I also try to move keystore and truststore setting to yaml, but these settings
do not work if they are only set to system property.
Is there a way to overwrite keystore and truststore settings after
configurations in yaml are loaded?
Or should I use SSLContext which loads specified keystore and truststore like
in
[SSLFactory.java|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/security/SSLFactory.java#L125],
and use it when create SslRMIServerSocketFactory instance?
Could anyone review this patch and please give me some advice.
Thanks.
> 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: Configuration
> Reporter: Sam Tunnicliffe
> Priority: Minor
> Labels: lhf
> Fix For: 3.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
(v6.3.4#6332)
