cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patricio Echague (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3403) describe_ring topology information is wrong/incomplete
Date Wed, 26 Oct 2011 17:45:34 GMT

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

Patricio Echague commented on CASSANDRA-3403:
---------------------------------------------

Patch tested with SimpleSnitch and PropertyFileSnitch for one and two datacenter.

Also tested using HectorAutoDiscoveryService.
                
> describe_ring topology information is wrong/incomplete
> ------------------------------------------------------
>
>                 Key: CASSANDRA-3403
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3403
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>            Assignee: Patricio Echague
>             Fix For: 1.0.1
>
>         Attachments: trunk-3403-v1.diff
>
>
> In CASSANDRA-2882, topology information was added to describe_ring, however it asks the
gossiper for the DC information, and the gossiper can only have this with a gossip-enabled
snitch, which currently means the Ec2Snitch.  Instead, it should be asking the snitch for
the DC for each endpoint.
> Also, the port information should just be removed: whatever port the client has connected
to in order to call describe_ring is the right port to use for all endpoints.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message