[MDEV-11006] Galera config on ipv6 only hosts - Jira

XML

Word

Printable

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:

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

relates to

MDEV-11314 MariaDB Galera Cluister issue with internal IPv6 GCOMM network

MDEV-17618 Galera SST IPv6 problems

MDEV-18797 Make mariabackup/xtrabackup-v2 SST script autodetect ipv6 addresses and add relevant socat option

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.