cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11107) Add native_transport_address and native_transport_broadcast_address yaml options
Date Wed, 30 Nov 2016 10:08:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708131#comment-15708131
] 

Sylvain Lebresne commented on CASSANDRA-11107:
----------------------------------------------

bq. Let me know what you think, [~slebresne].

Hum, I guess it's probably late enough in 3.0/3.X cycle to not bother with anything too complex.
I guess the main problem is 4.0 where using {{rpc_*}} will look really weird and arbitrary.
But I'm fine making this a 4.0 patch only by introducing the new names there as basically
a renaming of the old ones where:
* for the yaml, since it's a major upgrade, maybe it's fine to just start refusing the old
names and adding the new ones direclty.
* for the {{peers}}/{{local}} tables, we can add {{native_transport_address}} but keep {{rpc_address}}
(which will have the exact same value) temporarily as deprecated so drivers have time to update.
* for gossip, I believe we can just rename the {{ApplicationState}} enum but call it a day
otherwise.


> 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)

Mime
View raw message