-
I see that almost everything related to replication is missing in the autocompletion:
`CHANGE MASTER TO` ([MariaDB 10.x](https://mariadb.com/kb/en/mariadb/change-master-to/) )
`SHOW ALL SLAVES STATUS…
-
```
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. Have master-slave replication running ok.
2. Manually stop mysql on master
3. Let failover run
What is the expected output? What do you see instead?
Expe…
-
```
What steps will reproduce the problem?
1. Have master-slave replication running ok.
2. Manually stop mysql on master
3. Let failover run
What is the expected output? What do you see instead?
Expe…
-
```
What steps will reproduce the problem?
1. Have master-slave replication running ok.
2. Manually stop mysql on master
3. Let failover run
What is the expected output? What do you see instead?
Expe…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…
-
```
Hi
I have a mysql cluster with one master node and two hot standby slave nodes.
All reads and writes go to master. The three node cluster is managed by
corosync pacemaker that has a VIP for the…