[
https://issues.apache.org/jira/browse/CASSANDRA-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130375#comment-15130375
]
Sylvain Lebresne commented on CASSANDRA-11107:
----------------------------------------------
It's certainly not a bug as this is well documented in the yaml (look at both
the comment on {{rpc_address}} and the one on {{start_native_transport}}). Or
to put it another way, you might find the naming confusing, but {{rpc_address}}
is both a configuration for the thrift RPC and the native protocol server.
That said, with the thrift deprecation coming in 4.0 (and so the removal of
thrift rpc related options), it's probably worth transitioning to specific
{{native_transport_address}} and {{native_transport_broadcast_address}}, which
could default to the {{rpc_*}} ones if unset in 3.0 for backward compatibility.
That's a minor improvement however so I'll update the description and type of
this ticket.
> rpc_address is required for native protocol
> -------------------------------------------
>
> Key: CASSANDRA-11107
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11107
> Project: Cassandra
> Issue Type: Bug
> Components: Configuration
> Reporter: n0rad
> 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)
