You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#417 mentioned we should use ist.recv_bind in wsrep_provider_options to indicate the private ip if we are using AWS EC2. This works fine in MySQL Wresp 8 and Galera4. However it seems in MariaDB 10.6 and Galera4 the IST sender will try to connect via private ip to other nodes and fails. WSREP: IST failed: IST sender, failed to connect 'tcp://[private ip]:4568': Failed to connect 'tcp://[private ip]:4568': connect: Connection timed out: 110 (Connection timed out)
Can we tell sender to use public ip in wsrep_cluster_address?
The text was updated successfully, but these errors were encountered:
#417 mentioned we should use
ist.recv_bind
in wsrep_provider_options to indicate the private ip if we are using AWS EC2. This works fine in MySQL Wresp 8 and Galera4. However it seems in MariaDB 10.6 and Galera4 the IST sender will try to connect via private ip to other nodes and fails.WSREP: IST failed: IST sender, failed to connect 'tcp://[private ip]:4568': Failed to connect 'tcp://[private ip]:4568': connect: Connection timed out: 110 (Connection timed out)
Can we tell sender to use public ip in wsrep_cluster_address?
The text was updated successfully, but these errors were encountered: