cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9436) Expose rpc_address and listen_address of each Cassandra node
Date Fri, 29 May 2015 16:00:23 GMT

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

Piotr Kołaczkowski updated CASSANDRA-9436:
------------------------------------------
    Summary: Expose rpc_address and listen_address of each Cassandra node  (was: Expose private
rpc_address and listen_address of each Cassandra node)

> Expose rpc_address and listen_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
>
> 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?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message