[ https://issues.apache.org/jira/browse/CASSANDRA-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049649#comment-17049649 ]
Michael Semb Wever edited comment on CASSANDRA-15616 at 3/2/20 9:17 PM: ------------------------------------------------------------------------ ||branch||circleci||jenkins pipeline|| |[trunk_15616|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_15616]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Ftrunk_15616]|[!https://builds.apache.org/job/Cassandra-devbranch-pipeline/20/badge/icon!|https://builds.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/20]| was (Author: michaelsembwever): ||branch||circleci||jenkins pipeline||jenkins dtests|| |[trunk_15616|https://github.com/apache/cassandra/compare/trunk...thelastpickle:mck/trunk_15616]|[circleci|https://circleci.com/gh/thelastpickle/workflows/cassandra/tree/mck%2Ftrunk_15616]|[!https://builds.apache.org/job/Cassandra-devbranch-pipeline/20/badge/icon!|https://builds.apache.org/blue/organizations/jenkins/Cassandra-devbranch/detail/Cassandra-devbranch/20]| > 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 define that also 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