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

Chris Lohfink commented on CASSANDRA-15616:
-------------------------------------------

I walked through repo and your whitelist captured everything I could find. I 
would actually like to see removing `"java.class.path"` simply because it's so 
long makes the output unreadable without `EXPAND ON` and its pretty limited 
value. Added some small comments in 
https://github.com/apache/cassandra/commit/b226d3014b7cb13eb61b47bda2185fc1ccf0b1ef

> Expose Cassandra related system properties in a virtual table
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-15616
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15616
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/Virtual Tables
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: High
>             Fix For: 4.x
>
>
> Allow viewing Cassandra related system properties.
> Viewing yaml config settings, as implemented by {{SettingsTable}} in 
> CASSANDRA-14573, is not enough for certain third-party tool use-cases. There 
> are a number of system properties that can be defined that contribute to the 
> configuration set that Cassandra runs on.
> An example of such a use-case is described in CASSANDRA-15339. JMX ports need 
> to be discovered, especially in 4.0 where multiple nodes can run on one 
> ipaddress. Unlike the native port that is through gossip discoverable, the 
> jmx port is not. The jmx port is also not available via the SettingsTable. 
> With this patch and {{SystemPropertiesTable}} it becomes possible to first 
> discover all the native ports in the cluster and against each then discover 
> each node's jmx port.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to