-
```
What steps will reproduce the problem?
1. Set up single master, single slave, single MHA manager
2. Setup configuration file...
user=root
password=
ssh_user=mha
manager_workdir=/var/log/masterha/…
-
```
What steps will reproduce the problem?
1. Set up single master, single slave, single MHA manager
2. Setup configuration file...
user=root
password=
ssh_user=mha
manager_workdir=/var/log/masterha/…
-
```
What steps will reproduce the problem?
1. Set up single master, single slave, single MHA manager
2. Setup configuration file...
user=root
password=
ssh_user=mha
manager_workdir=/var/log/masterha/…
-
```
What steps will reproduce the problem?
1. Set up single master, single slave, single MHA manager
2. Setup configuration file...
user=root
password=
ssh_user=mha
manager_workdir=/var/log/masterha/…
-
**Describe the bug**
When I make the MySQL master as slave and slave as master, I found that the connections in used were block about 15min, and then I got the exception "tortoise.exceptions.Operatio…
-
```
When performing a controlled failover in a MySQL pair environment, if the
CHANGE MASTER works, but the SLAVE SLAVE fails (a connection issue), the new
slave still has read_only=FALSE.
By sim…
-
```
When performing a controlled failover in a MySQL pair environment, if the
CHANGE MASTER works, but the SLAVE SLAVE fails (a connection issue), the new
slave still has read_only=FALSE.
By sim…
-
```
When performing a controlled failover in a MySQL pair environment, if the
CHANGE MASTER works, but the SLAVE SLAVE fails (a connection issue), the new
slave still has read_only=FALSE.
By sim…
-
```
When performing a controlled failover in a MySQL pair environment, if the
CHANGE MASTER works, but the SLAVE SLAVE fails (a connection issue), the new
slave still has read_only=FALSE.
By sim…
-
```
What steps will reproduce the problem?
1. On three servers (CentOS 6, MariaDB 5.5) do the following installs:
Server 1: Primary MySQL master - startup MySQL. This will act as primary master…