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

Nick Bailey commented on CASSANDRA-1777:
----------------------------------------

Besides just auto_discovery this breaks the pig storage func in contrib if you 
use different interfaces. That class uses describe ring to generate the input 
splits for map tasks to work on, which obviously doesn't work if it returns the 
gossip interface instead of the thrift interface.

+1 on fixing this and backporting to 0.7

> 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

Reply via email to