You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Pavel Yaskevich (JIRA)" <ji...@apache.org> on 2011/09/12 21:05:09 UTC

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

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

Pavel Yaskevich resolved CASSANDRA-2882.
----------------------------------------

    Resolution: Fixed

Committed. Thanks, Mark!

> 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
>            Assignee: Mark Guzman
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1
>
>         Attachments: 0001-CASSANDRA-2882-feedback-changes.patch, 0001-CASSANDRA-2882-patch-w-o-generated-files.patch, 0001-CASSANDRA-2882-rebased.patch, 0001-added-the-host-addr-to-the-EndpointDetail-class.-det.patch, 0001-adding-an-additional-parameter-to-the-TokenRange-res.patch, 0001-final-cleaned-up-2882-changes.patch
>
>
> 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