[jira] [Created] (CASSANDRA-9603) Expose private listen_address in system.local

["Piotr Kołaczkowski (JIRA)" <ji...@apache.org>]

Piotr Kołaczkowski created CASSANDRA-9603:
---------------------------------------------

             Summary: Expose private listen_address in system.local
                 Key: CASSANDRA-9603
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9603
             Project: Cassandra
          Issue Type: Improvement
          Components: Core
            Reporter: Piotr Kołaczkowski


We had some hopes CASSANDRA-9436 would add it, yet it added rpc_address instead of both rpc_address *and* listen_address. We really need listen_address here, because we need to get information on the private IP C* binds to. Knowing this we could better match Spark nodes to C* nodes and process data locally in environments where rpc_address != listen_address like EC2. 

See, Spark does not know rpc addresses nor it has a concept of broadcast address. It only knows the hostname / IP its workers bind to. In case of cloud environments, these are private IPs. Now if we give Spark a set of C* nodes identified by rpc_addresses, Spark doesn't recognize them as belonging to the same cluster. It treats them as "remote" nodes and has no idea where to send tasks optimally. 



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