[ https://issues.apache.org/jira/browse/CASSANDRA-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706902#comment-15706902 ]
Joel Knighton edited comment on CASSANDRA-11107 at 11/29/16 11:28 PM: ---------------------------------------------------------------------- That's correct - it's true that I could at least piggyback on those since those migrations/changes would already be necessary. EDIT: That is, I would need to make additional changes, but I could time this for the same release to prevent the need for additional legacy tables. was (Author: jkni): That's correct - it's true that I could at least piggyback on those since those migrations/changes would already be necessary. > 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)