Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.18
-
Centos 7
Description
Hi,
I tried to setup a galera cluster with 10.1.18 on Centos 7 with ipv6 only hosts. The "normal" steup did not work and so I found:
http://blog.widodh.nl/2016/02/mariadb-galera-cluster-on-ipv6/
But this also did not work cause the crappy parsing in your scripts like:
*RSYNC_PORT=$(echo $ADDR | awk -F ':' '{ print $2 }')*
|
This will never work with Ipv6 addresses. All other scripts have also bugs like these:
*Using socat ipv4 only, from the manpage:
|
-4 Use IP version 4 in case that the addresses do not implicitly or
|
explicitly specify a version; this is the default.
|
|
|
-6 Use IP version 6 in case that the addresses do not implicitly or
|
explicitly specify a version.
|
*
|
Without -6 it will never work!!
I have now a running configuration using hostnames:
*
|
[galera]
|
# Mandatory settings
|
wsrep_on=ON
|
wsrep_provider=/usr/lib64/galera/libgalera_smm.so
|
wsrep_cluster_name="wso2"
|
wsrep_cluster_address="gcomm://db001.test.local,db002.test.local,db003.test.local"
|
wsrep_sst_auth=sst_user:sst_pass
|
wsrep_sst_method=rsync
|
binlog_format=row
|
default_storage_engine=InnoDB
|
innodb_autoinc_lock_mode=2
|
wsrep_node_name="db002"
|
wsrep_provider_options="gmcast.listen_addr=tcp://[::]:4567;ist.recv_addr=[XXXX:XXXX:XXXXX:XXXX:XXXXX:XXXX:XXXX:XXXX]:4568"
|
wsrep_node_address ="db002.test.local:4567"
|
wsrep_sst_receive_address="db002.test.local:4444"
|
*
|
Please fix the sst scripts to be full ipv6 compatible and fix the documentation!!
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
Activity
mariadb-server-10.3 1:10.3.15+maria~bionic
sst is still broken when wsrep_node_address is an ipv6 address. Seems to work if it's a hostname.
In my understanding this has been fixed on more recent versions.
Some of the issues on IPv6 has been addressed on later releases, can you please retest.