[
https://issues.apache.org/jira/browse/CASSANDRA-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689935#comment-15689935
]
Sylvain Lebresne commented on CASSANDRA-11107:
----------------------------------------------
Note: for things to not look too awkward in 4.0 (once thrift is removed), we
also probably want to add in a similar fashion than what's above:
* `native_transport_keepalive`: for some reason the native protocol server
reuse `rpc_keepalive`
* `native_transport_interface`: similar to `rpc_interface`
* `native_transport_interface_prefer_ipv6`: similar to
`rpc_interface_prefer_ipv6`
I'll also note that working on CASSANDRA-11115 and thinks look really weird
without those changes, so it would be nice if we could get this in relatively
quickly ([~jkni]: meaning, let me know if you don't think you'll have any cycle
for this in the next month or so).
> 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)
