replication-manager
replication-manager copied to clipboard
signal18
Signal 18 repman - Replication Manager for MySQL / MariaDB / Percona Server
When last slave is SlaveError or slaveLate and the master is in read pool , the master is drain leading to connection failure
When restoring backups with master binlogs it may be necessary to monitor all slaves and purge the binlog on master before oldest slave master binlogs to free space and purge...
We configured below replication-manager parameters to connect DB server OS via ssh. We can restart DB node from replication-manager as expected. prov-orchestrator = "onpremise" onpremise-ssh = true onpremise-ssh-credential = "root"...
When switchover, replication-manager will set read_only=1 in new slave (original master) DB nodes. This new slave (original master) has mysql variable read_only=0 in my.cnf. When we restart this new slave,...
In orchestrator onpremise if we define all db and proxy nodes using ip and proxy-servers-read-on-master=false Draining server does not work and so the detection of miss configuration never end 023/12/07...
Many logs options are not found in Web Gui adding a log subtab that enabling setting of verbose = false log-failed-election = true log-level = 1 log-sql-in-monitoring = true log-sst...
Work around enable multi-master-loop to fallback to master-slave via topology detection
How to reproduce Bootstrap a named source replication , switchover and rebootstrap Existing replication stream on channel is not reset so the topology is changed to loop Manual workaround reset...
Replicate_Do_Domain_Ids: Replicate_Ignore_Domain_Ids: Should be added to CHANGE MASTER helper
It 's always a bad idea to elect a server with lower version but could be sometime done for downgrade don't let this appen by default without user agreement via...