George, On Fri, Nov 2, 2018 at 7:01 PM George Diamantopoulos <georgediam@gmail.com> wrote:
Hello all,
I've setup a galera cluster with 3 nodes, and I believe that wsrep_node_incoming_address is not honoured when set in the configuration. More specifically, the setting persists in mariadb:
+-----------------------------+---------------+ | Variable_name | Value | +-----------------------------+---------------+ | bind_address | 172.30.20.1 | | wsrep_node_address | 172.30.20.129 | | wsrep_node_incoming_address | 172.30.20.129 | | wsrep_sst_receive_address | 172.30.20.129 | +-----------------------------+---------------+
But the process listens on all interfaces instead:
root@gal0-cn1:~# netstat -plunt | grep mysql tcp 0 0 172.30.20.1:3306 0.0.0.0:* LISTEN 17229/mysqld tcp 0 0 0.0.0.0:4567 0.0.0.0:* LISTEN 17229/mysqld
Is this expected behaviour? Shouldn't mysqld only listen on 172.30.20.129:4567, as configured? Thanks!
The option you are looking for is: https://mariadb.com/kb/en/library/wsrep_provider_options/#gmcastlisten_addr So in your case it would be: wsrep_provider_options="gmcast.listen_addr=tcp://173.30.20.129;<other options>" Please note you can also specify a custom port as: wsrep_provider_options="gmcast.listen_addr=tcp://173.30.20.129:9999;<other options>" That will require that the other nodes specify this custom port for in the cluster address for this node, e.g.: wsrep_cluster_address="gcomm://173.30.20.129:9999,<other nodes here>" One consequence of this is that you can setup multiple nodes on the same host (for testing purposes). Best Regards Claudio