[
https://issues.apache.org/jira/browse/CASSANDRA-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113613#comment-13113613
]
Jonathan Ellis commented on CASSANDRA-3214:
-------------------------------------------
But it's totally valid to have rpc_ on 0.0.0.0 and listen on something that
clients cannot connect to (separate interface, firewalled off, etc). So
fundamentally I think it comes down to "you shouldn't use 0.0.0.0 as
rpc_address if you're going to use describe_ring."
> Make CFIF use rpc_endpoint prior to trying endpoint
> ---------------------------------------------------
>
> Key: CASSANDRA-3214
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3214
> Project: Cassandra
> Issue Type: Improvement
> Components: Hadoop
> Affects Versions: 0.8.6
> Environment: Hadoop 0.20 / Cassandra 0.8.5 / Ubuntu 10.04 /
> Reporter: Eldon Stegall
> Assignee: Eldon Stegall
> Priority: Minor
> Fix For: 0.8.7, 1.0.0
>
> Attachments: CASSANDRA-3214-make-cfif-use-rpc-endpoints-v1.txt
>
>
> Following up on CASSANDRA-3187 , we probably need to attempt to use the
> rpc_endpoint address first, and then fall back to the gossip endpoint if we
> don't get what we want.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
