[
https://issues.apache.org/jira/browse/CASSANDRA-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707007#comment-15707007
]
Ariel Weisberg commented on CASSANDRA-11107:
--------------------------------------------
I already have code in that direction as part of 7544. I am adding
default_native_port which is used when dealing with nodes that don't publish
their native port. New version nodes gossip their native port along with the
address and that is used. native_port now specifies just the native port of the
instance using that yaml file and it doesn't need to match across the cluster.
Once a rolling upgrade is complete the configurations can safely diverge across
the cluster.
It works similarly for listen_address.
It's not going to happen quickly, and honestly it seems at risk for a Feb/March
release. I have to do a large amount of additional work to get the storage port
issue sorted out so it.
The incremental additional work for me to do the gossip and peers work is
negligible. Native protocol and fixing the client driver side is a bigger
issue. I have to update the java client anyways because it's not exposing the
cluster metadata in a way that allows tools like sstableloader to work with
multiple instances per node.
> Add native_transport_address and native_transport_broadcast_address yaml
> options
> --------------------------------------------------------------------------------
>
> Key: CASSANDRA-11107
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11107
> Project: Cassandra
> Issue Type: Improvement
> Components: Configuration
> Reporter: n0rad
> Assignee: Joel Knighton
> Priority: Minor
>
> I'm starting cassandra on a container with this /etc/hosts
> {quote}
> 127.0.0.1 rkt-235c219a-f0dc-4958-9e03-5afe2581bbe1 localhost
> ::1 rkt-235c219a-f0dc-4958-9e03-5afe2581bbe1 localhost
> {quote}
> I have the default configuration except :
> {quote}
> - seeds: "10.1.1.1"
> listen_address : 10.1.1.1
> {quote}
> cassandra will start listening on *127.0.0.1:9042*
> if I set *rpc_address:10.1.1.1* , even if *start_rpc: false*, cassandra will
> listen on 10.1.1.1
> Since rpc is not started, I assumed that *rpc_address* and
> *broadcast_rpc_address* will be ignored
> It took me a while to figure that. There may be something to do around this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
