mha4mysql-manager
mha4mysql-manager copied to clipboard
Development tree of Master High Availability Manager and tools for MySQL (MHA), Manager part
大家好,我在进行MHA故障切换时,并没有成功,报错信息如下,请大师指点,谢谢! Tue Aug 28 17:40:16 2018 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase.. Tue Aug 28 17:40:16 2018 - [info] Tue Aug 28 17:40:16 2018...
https://github.com/yoshinorim/mha4mysql-manager/blob/abe11f9abb74bc5886012ff5cc9e209fb9b093c1/lib/MHA/ServerManager.pm#L1500 Tue May 29 14:52:57 2018 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time.. Tue May 29 14:52:57 2018 - [info] ok. Tue May 29 14:52:57 2018...
i did installed the node manager , but when i tested masterha_check_repl ,it would pup-up the following error . masterha_check_repl --conf=/etc/masterha/app1.cnf 。。。。。。。。。。。。。。 Tue Jul 17 01:52:34 2018 - [info] GTID...
This errant transactions check is only performed if `--check_for_errant_transactions` is present on `masterha_master_switch` command line, default behavior is unchanged. If errant transactions are found, switch-over is aborted during Phase 1...
@grypyrg mysql 5.7 use channel replication change master to ...... FOR CHANNEL ......; mha can not switch
Hi, we have been using the mha4mysql-service for along time, but know we are trying to upgrade to mysql 5.7 (from 5.5 threw 5.6) but the mha4mysql-service won't start after...
According to the [documentation](https://github.com/yoshinorim/mha4mysql-manager/wiki/masterha_master_switch) masterha_master_switch supports the _--skip_disable_read_only_ flag but adding the flag causes error. **Actual result:** ``` $ masterha_master_switch --master_state=alive --conf=/etc/mha4mysql/some_config.conf --interactive=0 --skip_disable_read_only Unknown options: --skip_disable_read_only ``` **Expected result:**...
When doing online master failover, there's no way to set a list of slave options, such as ssl_ca_file, master_ssl, etc. Would be nice if there was a way to specify...
…ary_check failed we find something shold be better during checking masterha_secondary_check on MHA node. ## command secondary_check_script=masterha_secondary_check -s 172.17.16.245 -s 172.17.2.201 --port=60122 --user=mysql --master_host=xxx-db-0001 --master_ip=172.17.16.119 --master_port=3306 We find it will...