[
https://issues.apache.org/jira/browse/CASSANDRA-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103156#comment-13103156
]
Jonathan Ellis commented on CASSANDRA-3187:
-------------------------------------------
Does make it simpler to write a client that works against both latest-0.7 and
latest-0.8, though (for 0.8 >= 0.8.6).
Especially if we push 0.8.6 out quickly. For whatever reason it seems like
many 0.8 deployments haven't moved off of 0.8.1 yet.
> Return both listen_address and rpc_address through describe_ring
> ----------------------------------------------------------------
>
> Key: CASSANDRA-3187
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3187
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Nick Bailey
> Assignee: Nick Bailey
> Priority: Minor
> Fix For: 0.8.6, 1.0.0
>
> Attachments:
> 0001-0.8-Return-both-rpc-address-and-listen-address-with-the-.patch,
> 0001-1.0-Return-both-rpc-address-and-listen-address-with-the-.patch
>
>
> CASSANDRA-1777 changed describe_ring to return the rpc address associated
> with a node instead of the listen_address. This allows using different
> interfaces for listen_address and rpc_address, but breaks when rpc_address is
> set to something like 0.0.0.0.
> I think the describe_ring should just return both interfaces. We can add an
> optional field to the TokenRange struct that is 'listen_endpoints' or
> something similar and populate that with the listen addresses of nodes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
