[
https://issues.apache.org/jira/browse/CASSANDRA-9436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko updated CASSANDRA-9436:
-----------------------------------------
Description:
When running Cassandra nodes with collocated Spark nodes and accessing such
cluster from remote, to get data-locality right, we need to tell Spark the
locations of the Cassandra nodes and they should match the addresses that Spark
nodes bind to. Therefore in cloud environments we need to use private IPs for
that. Unfortunately, the client which connects from remote would know only the
broadcast rpc_addresses which are different.
Can we have the IP/hostname that every C* node binds to exposed in a system
table?
system.peers table contains that information, but it doesn't contain that
information for the local node.
So can we have broadcast_address and rpc_address added to the system.local
table?
was:
When running Cassandra nodes with collocated Spark nodes and accessing such
cluster from remote, to get data-locality right, we need to tell Spark the
locations of the Cassandra nodes and they should match the addresses that Spark
nodes bind to. Therefore in cloud environments we need to use private IPs for
that. Unfortunately, the client which connects from remote would know only the
broadcast rpc_addresses which are different.
Can we have the IP/hostname that every C* node binds to exposed in a system
table?
system.peers table contains that information, but it doesn't contain that
information for the local node.
So can we have listen_address and rpc_address added to the system.local table?
> Expose rpc_address and broadcast_address of each Cassandra node
> ---------------------------------------------------------------
>
> Key: CASSANDRA-9436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9436
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Piotr Kołaczkowski
> Assignee: Carl Yeksigian
> Fix For: 2.1.6, 2.0.16, 2.2.0 rc1
>
>
> When running Cassandra nodes with collocated Spark nodes and accessing such
> cluster from remote, to get data-locality right, we need to tell Spark the
> locations of the Cassandra nodes and they should match the addresses that
> Spark nodes bind to. Therefore in cloud environments we need to use private
> IPs for that. Unfortunately, the client which connects from remote would know
> only the broadcast rpc_addresses which are different.
> Can we have the IP/hostname that every C* node binds to exposed in a system
> table?
> system.peers table contains that information, but it doesn't contain that
> information for the local node.
> So can we have broadcast_address and rpc_address added to the system.local
> table?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
