You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Created) (JIRA)" <ji...@apache.org> on 2011/10/26 04:46:32 UTC
[jira] [Created] (CASSANDRA-3403) describe_ring topology
information is wrong/incomplete
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
Fix For: 1.0.1
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
[jira] [Updated] (CASSANDRA-3403) describe_ring topology
information is wrong/incomplete
Posted by "Patricio Echague (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patricio Echague updated CASSANDRA-3403:
----------------------------------------
Assignee: Patricio Echague
> 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
>
>
> 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
[jira] [Updated] (CASSANDRA-3403) describe_ring topology
information is wrong/incomplete
Posted by "Patricio Echague (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patricio Echague updated CASSANDRA-3403:
----------------------------------------
Attachment: trunk-3403-v1.diff
> 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
[jira] [Commented] (CASSANDRA-3403) describe_ring topology
information is wrong/incomplete
Posted by "Patricio Echague (Commented) (JIRA)" <ji...@apache.org>.
[ 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