[
https://issues.apache.org/jira/browse/CASSANDRA-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468444#comment-13468444
]
Sylvain Lebresne commented on CASSANDRA-4501:
---------------------------------------------
bq. I should also note that for 1.2, we've added 5 gossip states, and we have 5
padding states in 1.1, so we don't really have room to add anymore in this
release
Alright, for 1.2 I've created CASSANDRA-4751 and so I'm moving this to 1.3. As
said in CASSANDRA-4751, if nobody complains about having the same address for
thrift and the binary protocol, I'm good skipping that altogether.
On the "port issue", let it be clear that I don't care about allowing people to
use different ports on different machines. I do still think however that we
should start gossiping the ports if only to throw out an error (or a warning)
if people do use different ports on different host. Because allowing it
silently but not supporting it in other parts of the code is not the best user
experience imho. But that's by all mean a minor issue and is not specific to
the binary protocol.
> Gossip the ip and port used by the binary protocol
> --------------------------------------------------
>
> Key: CASSANDRA-4501
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4501
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.3
>
>
> Same as we gossip the rpc_address, we should add gossipping of the native
> transport address (including the port). CASSANDRA-4480 has one reason why we
> would want to do that.
--
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
