cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-1777) The describe_host API method is misleading in that it returns the interface associated with gossip traffic
Date Wed, 03 Aug 2011 19:24:27 GMT

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

Jonathan Ellis commented on CASSANDRA-1777:
-------------------------------------------

oh yeah.  the whole "gossip is for internal cluster state, we definitely shouldn't be using
it for rpc_address and rpc_port" thing I objected to originally.

however, I don't have a better solution (asking nodes directly would mean we couldn't include
nodes that are currently unreachable), so +1 I guess on the general approach.

if we're not going to expose individual rpc_port can we just require that it be the same cluster-wide
and not bother gossiping it?  it's kind of a misfeature anyway to allow different ones.

the old getRangeToEndpointMap is unused and can be removed now right?

Committing to 0.8 is probably fine but let's leave 0.7 alone.

> The describe_host API method is misleading in that it returns the interface associated
with gossip traffic
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1777
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1777
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Nate McCall
>            Assignee: Brandon Williams
>             Fix For: 1.0
>
>         Attachments: 1777.txt
>
>   Original Estimate: 16h
>  Remaining Estimate: 16h
>
> If the hardware is configured to use separate interfaces for thrift and gossip, the gossip
interface will be returned, given the results come out of the ReplicationStrategy eventually.
> I understand the approach, but given this is on the API, it effective worthless in situations
of host auto discovery via describe_ring from a client. I actually see this as the primary
use case of this method - why else would I care about the gossip iface from the client perspective?
It's current form should be relegated to JMX only. 
> At the same time, we should add port information as well. 
> describe_splits probably has similar issues.
> I see the potential cart-before-horse issues here and that this will probably be non-trivial
to fix, but I think "give me a set of all the hosts to which I can talk" is pretty important
from a client perspective.

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

        

Mime
View raw message