You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nate McCall (JIRA)" <ji...@apache.org> on 2011/07/14 21:46:00 UTC

[jira] [Commented] (CASSANDRA-2882) describe_ring should include datacenter/topology information

    [ https://issues.apache.org/jira/browse/CASSANDRA-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065496#comment-13065496 ] 

Nate McCall commented on CASSANDRA-2882:
----------------------------------------

This should be considered related to CASSANDRA-1777

I think both of these are crucial to providing clients that can take advantage of topologies. 

> describe_ring should include datacenter/topology information
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-2882
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2882
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API, Core
>            Reporter: Mark Guzman
>            Priority: Minor
>
> describe_ring is great for getting a list of nodes in the cluster, but it doesn't provide any information about the network topology which prevents it's use in a multi-dc setup. It would be nice if we added another list to the TokenRange object containing the DC information. 
> Optimally I could have ask any Cassandra node for this information and on the client-side prefer local nodes but be able to fail to remote nodes without requiring another lookup.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira