Open TingweiPei opened 6 years ago
Same here. It looks like it only works using local ipv6 address [::], but that's not usable to point to remote nodes of course. Apparently some problem with ipv6 scope_id resolution.
I can confirm that galera 25.3.26 fixes the IPv6 connection issue for me.
I have a 3-node cluster <node1,node2,node3>, where node
I can bootstrap the 3-node cluster with the following config, e.g. for node2: [mysqld] wsrep_on=ON skip-name-resolve=1 binlog_format=ROW default-storage-engine=innodb innodb_autoinc_lock_mode=2 innodb_locks_unsafe_for_binlog=1 innodb_doublewrite=1 max_connections=2048 query_cache_size=0 query_cache_type=0 bind_address=node2 wsrep_provider=/usr/lib64/galera/libgalera_smm.so wsrep_cluster_name="ratester" wsrep_cluster_address="gcomm://node1,node2,node3" wsrep_provider_options = gmcast.listen_addr=tcp://[fd00:be38:af4c:a9a6:0:ee39:f850:c5f2]:4567; wsrep_slave_threads=1 wsrep_certify_nonPK=1 wsrep_max_ws_rows=131072 wsrep_max_ws_size=1073741824 wsrep_debug=0 wsrep_convert_LOCK_to_trx=0 wsrep_retry_autocommit=1 wsrep_auto_increment_control=1 wsrep_drupal_282555_workaround=0 wsrep_causal_reads=0 wsrep_notify_cmd= wsrep_sst_method=rsync
The bind_address resolves to the same IPv6 address as the one in configured in gmcast.listen_addr
IST and SST automatically use the fqdn specified in bind_address, so all traffic goes through the same interface and IPv6 address.
@TingweiPei @claudionanni I created working galera.cnf config files that have a 3-server MariaDB 10.3 setup running in CentOS8. Here is the link to my repo with the config files and details on how to set everything up: IPv6-only Galeria Cluster config files I hope this helps!
CentOS 7.3 x64、MySQL 5.7.21、galera 3.24 I'm trying to build a multi-master galera cluster, that works when I use ipv4, but fails when I use ipv6. The first node can be started successfully, but the other node can't join the cluster, configuration and errors are as follows. /etc/my.cnf
log errors