cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4751) User rpc_address for binary protocol and change default port
Date Wed, 03 Oct 2012 18:28:07 GMT

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

Sylvain Lebresne commented on CASSANDRA-4751:
---------------------------------------------

{{endpoint}} is the listen_address of the node, but for event, we want to provide the address
on which the node can be joined by a client, hence StorageService.instance.getRpcaddress.
                
> User rpc_address for binary protocol and change default port
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-4751
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4751
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.0 beta 2
>
>         Attachments: 4751.txt
>
>
> The events mechanism of the binary protocol require that we know the address on which
other nodes can be joined (for the binary protocol). Hence CASSANDRA-4501. However, in 1.2
we've already burned all the padding in 1.1 gossip, so we can't gossip a new info (the binary
protocol address), so CASSANDRA-4501 will have to move to 1.3.
> But we do already gossip the rpc_address value, so an option is to make the binary protocol
bind on the rpc_address (but a specific port) rather than having it's own setting. This ticket
suggests to do that. Imo, there is little downside to do it: the thrift and binary transport
are not meant to be used together except during the transition from one to the other, and
even then having to use the same network interface is hardly a limitation (in other words,
even for 1.3, we might want to hold on CASSANDRA-4501 until someone comes with a compelling
use case for it).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message