Recently we moved from an architecture of MySQL databases with just one master in a single cloud provider to a multi cloud solution (two providers and two master).
The MHA that is available in one provider works perfectly, but now the MHA detects the new master-master model and tries to connect to the IP used by master. That is the normal behavior, but the IP is from a tunnel that redirects the MySQL traffic, and because of that the SSH fails.
Is there a way to force the SSH connection to another IP? For example, a public one.
Instead of using the MySQL IP of the master database configuration.
The point of all this, is to change the master in one cloud without major issues.
Hello,
Recently we moved from an architecture of MySQL databases with just one master in a single cloud provider to a multi cloud solution (two providers and two master).
The MHA that is available in one provider works perfectly, but now the MHA detects the new master-master model and tries to connect to the IP used by master. That is the normal behavior, but the IP is from a tunnel that redirects the MySQL traffic, and because of that the SSH fails.
Is there a way to force the SSH connection to another IP? For example, a public one. Instead of using the MySQL IP of the master database configuration.
The point of all this, is to change the master in one cloud without major issues.
Regards.