首页 > 数据库 >MySQL MHA配置

MySQL MHA配置

时间：2024-01-23 15:02:46浏览次数：29  
标签：配置 14 126.130 MySQL 192.168 MHA mysql 2014 Oct

 MySQL环境：

     master：192.168.202.129:3306

     slave：192.168.202.129:3307，192.168.202.129:3307，192.168.202.130:3306，192.168.202.130:3307，192.168.202.130:3308

     MariaDB-10.0.13

     MHA环境：

     manager：192.168.202.129

     node：192.168.202.130(3306端口监听的实例作为备用主库)，192.168.202.129

     下载地址：http://code.google.com/p/mysql-master-ha/ （这个需要FQ），我在百度网盘里共享了一份：http://pan.baidu.com/s/1pJ0VkSz

     一 MySQL安装准备：

     1 建立MySQL安装目录：mkdir -p /usr/local/mysql

     2 建立mysql用户：

     

groupadd mysql
useradd -g mysql mysql

    3 下载依赖包：

    

yum  install make apr* autoconf automake curl curl-devel gcc gcc-c++ gtk+-devel zlib-devel openssl openssl-devel pcre-devel gd kernel keyutils patch perl kernel-headers compat*  cpp glibc libgomp libstdc++-devel keyutils-libs-devel libsepol-devel libselinux-devel krb5-devel  libXpm* freetype freetype-devel freetype* fontconfig fontconfig-devel  libjpeg* libpng* php-common php-gd gettext gettext-devel ncurses* libtool* libxml2 libxml2-devel patch policycoreutils bison

    4 下载cmake：yum install cmake -y

    5 开始编译：

    

cmake . -DCMAKE_INSTALL_PREFIX=/usr/local/mysql -DMYSQL_DATADIR=/home/mysql/data -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_general_ci -DEXTRA_CHARSETS=all -DENABLED_LOCAL_INFILE=1

    6 结束之后，输入下面的命令：make && make install

    上面的过程结束之后就安装好了MySQL。下面是配置过程：

   二 编译安装MySQL：

   1 修改环境变量：vi /etc/profile，添加下面的语句：

   

export PATH=$PATH:/usr/local/mysql/bin

   2 source /etc/profile加载环境变量

   3 将/usr/local/mysql/support_files下的my-default.cnf复制到/etc下：cp /usr/local/mysql/support_files/my-default.cnf /etc/my.cnf，修改这个文件加入下面的内容：

   

[mysqld_multi]
mysqld = /usr/local/mysql/bin/mysqld_safe
mysqladmin = /usr/local/mysql/bin/mysqladmin
log = /home/mysql/mydata/log/mysqld_multi.log


[mysqld1]
socket = /home/mysql/mydata/data1/socket/mysqld.sock
port = 3306
pid-file = /home/mysql/mydata/data1/mysqld.pid
datadir = /home/mysql/mydata/data1

log_bin=/home/mysql/mydata/data1/binlog/mysql-bin
server-id = 1

[mysqld2]
socket = /home/mysql/mydata/data2/socket/mysqld.sock
port = 3307
pid-file = /home/mysql/mydata/data2/mysqld.pid
datadir = /home/mysql/mydata/data2

log_bin=/home/mysql/mydata/data2/binlog/mysql-bin
server-id = 2
relay_log = /home/mysql/mydata/data2/relay_log/mysql-relay-bin
log_slave_updates = 1
read_only = 1

[mysqld3]
socket = /home/mysql/mydata/data3/socket/mysqld.sock
port = 3308
pid-file = /home/mysql/mydata/data3/mysqld.pid
datadir = /home/mysql/mydata/data3

log_bin=/home/mysql/mydata/data3/binlog/mysql-bin
server-id = 3
relay_log = /home/mysql/mydata/data3/relay_log/mysql-relay-bin
log_slave_updates = 1
read_only = 1

     上面的路径都需要用mysql用户建立，这里不再赘述。

     4 下面就可以初始化数据库了：

     

/usr/local/mysql/scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --datadir=/home/mysql/mydata/data1

/usr/local/mysql/scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --datadir=/home/mysql/mydata/data2

/usr/local/mysql/scripts/mysql_install_db --user=mysql --basedir=/usr/local/mysql --datadir=/home/mysql/mydata/data3

    这样就把一个服务器上所有的数据库都建立好了，在130服务器上也是如法炮制，不过在修改my.cnf的时候要注意一点就是修改server-id，从4以后开始，不要和129服务器的相同。

    下面就可以启动数据库了，命令很简单：

    

mysqld_multi --defaults-extra-file=/etc/my.cnf start 1,2,3

    这就将三个数据库启动好了，可以用下面的语句检查：

    

mysqld_multi --defaults-extra-file=/etc/my.cnf report

MySQL server from group: mysqld1 is running
MySQL server from group: mysqld2 is running
MySQL server from group: mysqld3 is running

    

     三 主从配置

     1 主库建立复制用户：

     

在192.168.202.129上：
$mysql -uroot -P3306 -p127.0.0.1

grant replication slave, replication client on *.* to repl@'192.168.202.%' identified by 'repl'; -- 这里限制在局域网内

    2 从库配置：

    

在192.168.202.129上：
$mysql -uroot -P3307 -p127.0.0.1
change master to master_host='192.168.202.129', MASTER_PORT=3306, master_user='repl', master_password='repl', master_log_file='mysql-bin.000001', master_log_pos=0;
start slave;
$mysql -uroot -P3308 -p127.0.0.1
change master to master_host='192.168.202.129', MASTER_PORT=3306, master_user='repl', master_password='repl', master_log_file='mysql-bin.000001', master_log_pos=0;
start slave;
在192.168.202.130上：
$mysql -uroot -P3306 -p127.0.0.1
change master to master_host='192.168.202.129', MASTER_PORT=3306, master_user='repl', master_password='repl', master_log_file='mysql-bin.000001', master_log_pos=0;
start slave;
$mysql -uroot -P3307 -p127.0.0.1
change master to master_host='192.168.202.129', MASTER_PORT=3306, master_user='repl', master_password='repl', master_log_file='mysql-bin.000001', master_log_pos=0;
start slave;
$mysql -uroot -P3308 -p127.0.0.1
change master to master_host='192.168.202.129', MASTER_PORT=3306, master_user='repl', master_password='repl', master_log_file='mysql-bin.000001', master_log_pos=0;
start slave;

     这样子就配置结束了。

     3 配置好了以后主库上会有slave过来的进程：

     mysql>show processlist;

     

MySQL MHA配置_mysql

     有几个slave，这里就会有多少个进程。

     4 

# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/bin/mysqlbinlog
# ln -s /usr/local/mysql/bin/mysql /usr/bin/mysql

 

     三 MHA配置

     1 依赖安装：

     在node节点上，执行下面的命令：

     

# yum install perl-DBD-MySQL

    在manager节点上：

    

# yum install perl-DBD-MySQL
# yum install perl-Config-Tiny
# yum install perl-Log-Dispatch
# yum install perl-Parallel-ForkManager
# yum install -y rrdtool perl-rrdtool rrdtool-devel perl-Params-Validate

    2 rpm包安装：

    manager节点：

    

# rpm -ivh mha4mysql-manager-0.56-0.el6.noarch.rpm
# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm

   node节点：

   

# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm

    3 配置

    

mkdir -p /etc/masterha/
mkdir -p /var/log/masterha/app1/

    将下面的内容写进/etc/masterha/app1.cnf:

[server default]
manager_workdir=/var/log/masterha/app1
manager_log=/var/log/masterha/app1/manager.log
user=admin
password=admin
ssh_user=root
repl_user=repl
repl_password=repl
ping_interval=1
shutdown_script=""
master_ip_online_change_script=""
report_script=""


[server1]
hostname=192.168.126.129
port=3306
candidate_master=1
master_binlog_dir="/home/mysql/mydata/data1/binlog"


[server2]
hostname=192.168.126.130
port=3306
candidate_master=1
master_binlog_dir="/home/mysql/mydata/data1/binlog"

[server3]
hostname=192.168.126.130
port=3307

[server4]
hostname=192.168.126.130
port=3308

[server5]
hostname=192.168.126.129
port=3307

[server6]
hostname=192.168.126.129
port=3308

    4 配置ssh免秘钥：

# ssh-keygen -t rsa
# cd ~/.ssh
# cat id_rsa.pub >> authorized_keys
# chmod 600 authorized_keys

    将id_rsa.pub的内容粘贴到另一台服务器的~/.ssh/authorized_keys里（保证两个机器互相信任）。

    5 测试一下ssh： 

masterha_check_ssh --conf=/etc/masterha/app1.cnf

    下面的结果出来就对了：

    

Sat Oct 18 14:04:43 2014 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Oct 18 14:04:43 2014 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Oct 18 14:04:43 2014 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Oct 18 14:04:43 2014 - [info] Starting SSH connection tests..
Sat Oct 18 14:06:29 2014 - [debug]
Sat Oct 18 14:04:46 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.129:22) to [email protected](192.168.126.129:22)..
Sat Oct 18 14:05:07 2014 - [debug]   ok.
Sat Oct 18 14:05:07 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.129:22) to [email protected](192.168.126.130:22)..
Sat Oct 18 14:05:28 2014 - [debug]   ok.
Sat Oct 18 14:05:28 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.129:22) to [email protected](192.168.126.130:22)..
Sat Oct 18 14:05:49 2014 - [debug]   ok.
Sat Oct 18 14:05:49 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.129:22) to [email protected](192.168.126.130:22)..
Sat Oct 18 14:06:10 2014 - [debug]   ok.
Sat Oct 18 14:06:10 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.129:22) to [email protected](192.168.126.129:22)..
Sat Oct 18 14:06:29 2014 - [debug]
Sat Oct 18 14:04:45 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.130:22) to [email protected](192.168.126.129:22)..
Sat Oct 18 14:05:06 2014 - [debug]   ok.
Sat Oct 18 14:05:06 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.130:22) to [email protected](192.168.126.130:22)..
Sat Oct 18 14:05:27 2014 - [debug]   ok.
Sat Oct 18 14:05:27 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.130:22) to [email protected](192.168.126.130:22)..
Sat Oct 18 14:05:48 2014 - [debug]   ok.
Sat Oct 18 14:05:48 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.130:22) to [email protected](192.168.126.129:22)..
Sat Oct 18 14:06:09 2014 - [debug]   ok.
Sat Oct 18 14:06:09 2014 - [debug]  Connecting via SSH from [email protected](192.168.126.130:22) to [email protected](192.168.126.129:22)..
Sat Oct 18 14:06:31 2014 - [info] All SSH connection tests passed successfully.

    6 测试一下复制：

    

masterha_check_repl --conf=/etc/masterha/app1.cnf
Sat Oct 18 14:12:45 2014 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Oct 18 14:12:45 2014 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Oct 18 14:12:45 2014 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Oct 18 14:12:45 2014 - [info] MHA::MasterMonitor version 0.56.
Sat Oct 18 14:12:46 2014 - [info] GTID failover mode = 0
Sat Oct 18 14:12:46 2014 - [info] Dead Servers:
Sat Oct 18 14:12:46 2014 - [info] Alive Servers:
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.130(192.168.126.130:3306)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.130(192.168.126.130:3307)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.130(192.168.126.130:3308)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.129(192.168.126.129:3307)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.129(192.168.126.129:3308)
Sat Oct 18 14:12:46 2014 - [info] Alive Slaves:
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.130(192.168.126.130:3306)  Version=10.0.13-MariaDB-log (oldest major version between slaves) log-bin:enabled
Sat Oct 18 14:12:46 2014 - [info]     Replicating from 192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info]     Primary candidate for the new Master (candidate_master is set)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.130(192.168.126.130:3307)  Version=10.0.13-MariaDB-log (oldest major version between slaves) log-bin:enabled
Sat Oct 18 14:12:46 2014 - [info]     Replicating from 192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.130(192.168.126.130:3308)  Version=10.0.13-MariaDB-log (oldest major version between slaves) log-bin:enabled
Sat Oct 18 14:12:46 2014 - [info]     Replicating from 192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.129(192.168.126.129:3307)  Version=10.0.13-MariaDB-log (oldest major version between slaves) log-bin:enabled
Sat Oct 18 14:12:46 2014 - [info]     Replicating from 192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info]   192.168.126.129(192.168.126.129:3308)  Version=10.0.13-MariaDB-log (oldest major version between slaves) log-bin:enabled
Sat Oct 18 14:12:46 2014 - [info]     Replicating from 192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info] Current Alive Master: 192.168.126.129(192.168.126.129:3306)
Sat Oct 18 14:12:46 2014 - [info] Checking slave configurations..
Sat Oct 18 14:12:46 2014 - [info]  read_only=1 is not set on slave 192.168.126.130(192.168.126.130:3306).
Sat Oct 18 14:12:46 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.126.130(192.168.126.130:3306).
Sat Oct 18 14:12:46 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.126.130(192.168.126.130:3307).
Sat Oct 18 14:12:46 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.126.130(192.168.126.130:3308).
Sat Oct 18 14:12:46 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.126.129(192.168.126.129:3307).
Sat Oct 18 14:12:46 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.126.129(192.168.126.129:3308).
Sat Oct 18 14:12:46 2014 - [info] Checking replication filtering settings..
Sat Oct 18 14:12:46 2014 - [info]  binlog_do_db= , binlog_ignore_db=
Sat Oct 18 14:12:46 2014 - [info]  Replication filtering check ok.
Sat Oct 18 14:12:46 2014 - [info] GTID (with auto-pos) is not supported
Sat Oct 18 14:12:46 2014 - [info] Checking MHA Node version..
Sat Oct 18 14:13:40 2014 - [info]  Version check ok.
Sat Oct 18 14:13:40 2014 - [info] Checking SSH publickey authentication settings on the current master..
Sat Oct 18 14:13:45 2014 - [warning] HealthCheck: Got timeout on checking SSH connection to 192.168.126.129! at /usr/share/perl5/vendor_perl/MHA/HealthCheck.pm line 342.
Sat Oct 18 14:13:45 2014 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Sat Oct 18 14:13:45 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=192.168.126.130 --slave_ip=192.168.126.130 --slave_port=3306 --workdir=/var/tmp --target_version=10.0.13-MariaDB-log --manager_version=0.56 --relay_log_info=/home/mysql/mydata/data1/relay-log.info  --relay_dir=/home/mysql/mydata/data1/  --slave_pass=xxx
Sat Oct 18 14:13:45 2014 - [info]   Connecting to [email protected](192.168.126.130:22)..
  Checking slave recovery environment settings..
    Opening /home/mysql/mydata/data1/relay-log.info ... ok.
    Relay log found at /home/mysql/mydata/data1, up to mysqld-relay-bin.000002
    Temporary relay log file is /home/mysql/mydata/data1/mysqld-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Sat Oct 18 14:13:56 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=192.168.126.130 --slave_ip=192.168.126.130 --slave_port=3307 --workdir=/var/tmp --target_version=10.0.13-MariaDB-log --manager_version=0.56 --relay_log_info=/home/mysql/mydata/data2/relay-log.info  --relay_dir=/home/mysql/mydata/data2/  --slave_pass=xxx
Sat Oct 18 14:13:56 2014 - [info]   Connecting to [email protected](192.168.126.130:22)..
  Checking slave recovery environment settings..
    Opening /home/mysql/mydata/data2/relay-log.info ... ok.
    Relay log found at /home/mysql/mydata/data2/relay_log, up to mysql-relay-bin.000002
    Temporary relay log file is /home/mysql/mydata/data2/relay_log/mysql-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Sat Oct 18 14:14:21 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=192.168.126.130 --slave_ip=192.168.126.130 --slave_port=3308 --workdir=/var/tmp --target_version=10.0.13-MariaDB-log --manager_version=0.56 --relay_log_info=/home/mysql/mydata/data3/relay-log.info  --relay_dir=/home/mysql/mydata/data3/  --slave_pass=xxx
Sat Oct 18 14:14:21 2014 - [info]   Connecting to [email protected](192.168.126.130:22)..
  Checking slave recovery environment settings..
    Opening /home/mysql/mydata/data3/relay-log.info ... ok.
    Relay log found at /home/mysql/mydata/data3/relay_log, up to mysql-relay-bin.000002
    Temporary relay log file is /home/mysql/mydata/data3/relay_log/mysql-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Sat Oct 18 14:14:47 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=192.168.126.129 --slave_ip=192.168.126.129 --slave_port=3307 --workdir=/var/tmp --target_version=10.0.13-MariaDB-log --manager_version=0.56 --relay_log_info=/home/mysql/mydata/data2/relay-log.info  --relay_dir=/home/mysql/mydata/data2/  --slave_pass=xxx
Sat Oct 18 14:14:47 2014 - [info]   Connecting to [email protected](192.168.126.129:22)..
  Checking slave recovery environment settings..
    Opening /home/mysql/mydata/data2/relay-log.info ... ok.
    Relay log found at /home/mysql/mydata/data2/relay_log, up to mysql-relay-bin.000002
    Temporary relay log file is /home/mysql/mydata/data2/relay_log/mysql-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Sat Oct 18 14:14:58 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='admin' --slave_host=192.168.126.129 --slave_ip=192.168.126.129 --slave_port=3308 --workdir=/var/tmp --target_version=10.0.13-MariaDB-log --manager_version=0.56 --relay_log_info=/home/mysql/mydata/data3/relay-log.info  --relay_dir=/home/mysql/mydata/data3/  --slave_pass=xxx
Sat Oct 18 14:14:58 2014 - [info]   Connecting to [email protected](192.168.126.129:22)..
  Checking slave recovery environment settings..
    Opening /home/mysql/mydata/data3/relay-log.info ... ok.
    Relay log found at /home/mysql/mydata/data3/relay_log, up to mysql-relay-bin.000002
    Temporary relay log file is /home/mysql/mydata/data3/relay_log/mysql-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Sat Oct 18 14:15:10 2014 - [info] Slaves settings check done.
Sat Oct 18 14:15:10 2014 - [info]
192.168.126.129(192.168.126.129:3306) (current master)
 +--192.168.126.130(192.168.126.130:3306)
 +--192.168.126.130(192.168.126.130:3307)
 +--192.168.126.130(192.168.126.130:3308)
 +--192.168.126.129(192.168.126.129:3307)
 +--192.168.126.129(192.168.126.129:3308)

Sat Oct 18 14:15:10 2014 - [info] Checking replication health on 192.168.126.130..
Sat Oct 18 14:15:10 2014 - [info]  ok.
Sat Oct 18 14:15:10 2014 - [info] Checking replication health on 192.168.126.130..
Sat Oct 18 14:15:10 2014 - [info]  ok.
Sat Oct 18 14:15:10 2014 - [info] Checking replication health on 192.168.126.130..
Sat Oct 18 14:15:10 2014 - [info]  ok.
Sat Oct 18 14:15:10 2014 - [info] Checking replication health on 192.168.126.129..
Sat Oct 18 14:15:10 2014 - [info]  ok.
Sat Oct 18 14:15:10 2014 - [info] Checking replication health on 192.168.126.129..
Sat Oct 18 14:15:10 2014 - [info]  ok.
Sat Oct 18 14:15:10 2014 - [warning] master_ip_failover_script is not defined.
Sat Oct 18 14:15:10 2014 - [warning] shutdown_script is not defined.
Sat Oct 18 14:15:10 2014 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

    这样就OK了。

    7 开启masterha_manager

# nohup masterha_manager --conf=/etc/masterha/app1.cnf > /tmp/mha_manager.log  2>&1 &

   看一下状态：

# masterha_check_status --conf=/etc/masterha/app1.cnf 

app1 (pid:5161) is running(0:PING_OK), master:192.168.126.129

   这个时候也可以检测一下日志，可以新开一个terminal：

   tail -f /var/log/masterha/app1/manager.log

   8 测试一下断掉129的3306以后能不能切换到130的3306：

[root@bogon ~]# mysqld_multi --defaults-extra-file=/etc/my.cnf stop 1

   但是这之前确保没有这个文件 /var/log/masterha/app1/app1.failover.complete

   关掉实例之后就会发现刚才tail的日志不停的刷新，摘Failover Report出来：

  

----- Failover Report -----

app1: MySQL Master failover 192.168.126.129(192.168.126.129:3306) to 192.168.126.130(192.168.126.130:3306) succeeded

Master 192.168.126.129(192.168.126.129:3306) is down!

Check MHA Manager logs at bogon:/var/log/masterha/app1/manager.log for details.

Started automated(non-interactive) failover.
The latest slave 192.168.126.130(192.168.126.130:3306) has all relay logs for recovery.
Selected 192.168.126.130(192.168.126.130:3306) as a new master.
192.168.126.130(192.168.126.130:3306): OK: Applying all logs succeeded.
192.168.126.130(192.168.126.130:3307): This host has the latest relay log events.
192.168.126.130(192.168.126.130:3308): This host has the latest relay log events.
192.168.126.129(192.168.126.129:3307): This host has the latest relay log events.
192.168.126.129(192.168.126.129:3308): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
192.168.126.130(192.168.126.130:3308): OK: Applying all logs succeeded. Slave started, replicating from 192.168.126.130(192.168.126.130:3306)
192.168.126.130(192.168.126.130:3307): OK: Applying all logs succeeded. Slave started, replicating from 192.168.126.130(192.168.126.130:3306)
192.168.126.129(192.168.126.129:3307): OK: Applying all logs succeeded. Slave started, replicating from 192.168.126.130(192.168.126.130:3306)
192.168.126.129(192.168.126.129:3308): OK: Applying all logs succeeded. Slave started, replicating from 192.168.126.130(192.168.126.130:3306)
192.168.126.130(192.168.126.130:3306): Resetting slave info succeeded.
Master failover to 192.168.126.130(192.168.126.130:3306) completed successfully.

    9 下面看看是不是已经切过来了，登陆到130的3306上看一下processlist：

    

MySQL MHA配置_MySQL_02

    确实是四个，再看看129的3307的slave status：

    

MySQL MHA配置_perl_03

    已经切换到了130的3306上。

    再看看130的3307上：

    

MySQL MHA配置_mysql_04

    这个配置起来不是很复杂，我觉得基本所有的开源项目安装配置都不难，关键都是在参数的配置上，下面是我参考的文档，有自己的也有别人的：

    http://ylw6006.blog.51cto.com/470441/890360/

    http://www.jb51.net/LINUXjishu/128753.html

   

   



标签：配置,14,126.130,MySQL,192.168,MHA,mysql,2014,Oct
From： https://blog.51cto.com/u_16532032/9380067

相关文章

  • mysql mha 主从自动切换 高可用
    mha（MasterHighAvailability）目前在MySQL多服务器（超过二台），高可用方面是一个相对成熟的解决方案。 一，什么是mha，有什么特性1.主服务器的自动监控和故障转移MHA监控复制架构的主服务器，一旦检测到主服务器故障，就会自动进行故障转移。即使有些从服务器没有收到最新的relaylog，MHA自动......
  • mysql innobackupex xtrabackup 大数据量 备份 还原
    大数据量备份与还原，始终是个难点。当MYSQL超10G，用mysqldump来导出就比较慢了。在这里推荐xtrabackup,这个工具比mysqldump要快很多。 一、Xtrabackup介绍1，Xtrabackup是什么Xtrabackup是一个对InnoDB做数据备份的工具，支持在线热备份(备份时不影响数据读写)，是商业备份工具InnoDBHot......
  • noiLinux 入场配置 备忘
     1、配置basic/*Codebypp_orange*/#include<bits/stdc++.h>#definem_p(a,b)make_pair(a,b)#definepbpush_back#definelllonglong#defineldlongdouble#defineinf0x7fffffff//7f#defineinff0xfffffffffffffff//15f#definerep(i,l,r)fo......
  • mysql 查询所有表
    MySQL是一种开源的关系型数据库管理系统，在各种Web应用中使用广泛，因为它是高度可定制且易于管理的。MySQL包含一组操作，使您可以创建，更新和查询数据库中的数据。其中一个重要操作是查询所有表的数据，本文将介绍如何实现这一操作。一、使用SHOWTABLES命令SHOWTABLES命令是最简单和......
  • mysql权限的一个细枝
    业务需求：对一个用户回收一个表的所有权限，但是之前对这个用户是授权表所在库的整个权。 背景：某个表后来插入了机密数据，不能再让人随便查阅了。  比如：存在库test01 库下存在表T1，那mysql是否支持呢，来复盘下整个操作：  首先整库授权： grantallprivilgesontest01.*to......
  • Alpine基础环境配置
    Alpine基础环境配置版本的选择，默认使用standard，extend版本可做便携版本使用。用户手册：AlpineUserHandbook官方WIKI：AlpineLinuxWIKI安装安装的实际逻辑是通过setup-alpine​脚本去调用其他功能的脚本进行配置，可以通过vi查看脚本。如果某个部分安装失败，可退出后单独......
  • mysql分析sql语句基础工具 -- explain
    分析sql语句explainexplain(sql语句)G;分析结果：idsql语句编号如果是连接查询，表之间是平等关系，编号相同；如果有子查询，编号递增。select——type查询类型table查询针对的表 该值可能是实际的表名或者临时表，derived表示form子查询，null表示无须查表possible_key可能用到的索引ke......
  • MySQL 8.0 的xtrabackup备份
     xtrabackup备份语句：   fname=`date+%F_%H-%M-%S`mkdir-p/mnt/dbbak/db_$fnamextrabackup--defaults-file=/etc/my.cnf-uhyb-phd-h/var/lib/mysql-S/var/lib/mysql/mysql.sock-Hlocalhost--port=3306--backup--parallel=4--target-dir=/mnt/dbbak/db_$f......
  • mysql之my.cnf详解
    值，如果该值为0，则默认值为max_binlog_size(1G)；如果不为0，则max_relay_log_size则为最大的relay_log文件大小；relay-log-purge=1#是否自动清空不再需要中继日志时。默认值为1(启用)expire_logs_days=30#超过30天的binlog删除binlog_cache_size=1M#在一个事务中......
  • 随Linux开机自动启动mysql
    在MySQL的管理过程中，会遇到PCServer脱机或者重启，我需要在主机启动后再将MySQL服务启动。如果上百台或者更多的MySQL主机进行维护时，可能会有多台主机出现类似问题，要是每次都手动操作，是很繁琐的事情。我们可以采用随系统一起启动MySQL服务，这样就解决了频繁手动启动MySQL的问题。要实......

赞助商

阅读排行

网站主页关于我们联系我们网站地图

本网站内容转载自其他媒体，侵权联系[admin##ips99.com]。

Copyright © 2020-2023 IPS99 版权所有 IPS99