cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Semb Wever (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-15339) Make available the known JMX endpoints across the cluster
Date Fri, 04 Oct 2019 18:28:00 GMT


Michael Semb Wever updated CASSANDRA-15339:
    Reporter: Michael Semb Wever  (was: Morten Kuhl)

> Make available the known JMX endpoints across the cluster
> ---------------------------------------------------------
>                 Key: CASSANDRA-15339
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Gossip
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>              Labels: 4.0-feature-freeze-review-requested
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message