cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Guzman (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2882) describe_ring should include datacenter/topology information
Date Sat, 10 Sep 2011 02:53:09 GMT


Mark Guzman updated CASSANDRA-2882:

    Attachment: 0001-added-the-host-addr-to-the-EndpointDetail-class.-det.patch

Adding the host addr to the EndpointDetail class and only returning the subset having a port
or datacenter value.

> describe_ring should include datacenter/topology information
> ------------------------------------------------------------
>                 Key: CASSANDRA-2882
>                 URL:
>             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:


View raw message