cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Semb Wever (Jira)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-15339) Make available the known JMX endpoints across the cluster
Date Mon, 14 Oct 2019 14:30:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Semb Wever updated CASSANDRA-15339:
-------------------------------------------
    Description: 
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.

And example of the difficulty can be illustrated through the potential workaround…
Such a third-party tool could make a native protocol connection, and via the driver obtain
the list of all possible `host:port` native protocol connections, and make a connection to
each of these then requesting the configuration virtual table, from which the jmx port can
be obtained.

  was:
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.


> 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
>              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.
> And example of the difficulty can be illustrated through the potential workaround…
> Such a third-party tool could make a native protocol connection, and via the driver obtain
the list of all possible `host:port` native protocol connections, and make a connection to
each of these then requesting the configuration virtual table, from which the jmx port can
be obtained.



--
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


Mime
View raw message