You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2019/09/27 17:50:00 UTC
[jira] [Updated] (CASSANDRA-15339) Make available the known JMX
endpoints across the cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-15339:
-------------------------------------------
Change Category: Operability
Complexity: Normal
Status: Open (was: Triage Needed)
> Make available the known JMX endpoints across the cluster
> ---------------------------------------------------------
>
> Key: CASSANDRA-15339
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15339
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Gossip
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
>
> With the addition of multiple nodes running on the same server using different ports: CASSANDRA-7544 ; it becomes more difficult for third-party tools to easily connect to all nodes based on the jmx connection details to just one node.
> By adding jmx host and port to gossip, and saving it in {{system.peers_v2}}, the list of all jmx endpoints in a cluster can be fetch after just the initial successful jmx connection and the {{StorageServiceMBean.getJmxEndpoints()}} method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org