MySQL备份及主从复制
一、编写脚本，支持让用户自主选择，使用mysqldump还是xtraback全量备份。
#!/bin/bash
while true;do
cat << EOF
1) mysqldump
2) xtrabackup
3) quit
EOFread -p "请选择备份方式：" numcase $num in1)mkdir /backup/mysqldumpmysqldump -A -F --master-data --single-transaction > /backup/mysqldump/fullbsk_`date +%F`.sqlecho "成功备份到/backup/mysqldump"exit 1;;2)mkdir /backup/xtrabackxtrabackup --backup --target-dir=/backup/xtraback/`date +%F`/ &> /dev/nullecho "成功备份到/backup/xtraback"exit 2;;3)exit 3;;*);;esac
done
二、配置Mysql主从同步。
配置MySQL主节点
1.安装mariadb,修改配置文件[root@centos7 ~]#yum install mariadb-server -y
[root@centos7 ~]#vim /etc/my.cnf
[mysqld]
server-id=7
log-bin=/data/logbin/mysql
innodb_file_per_table=1
...
[root@centos7 ~]#mkdir /data/logbin
[root@centos7 ~]#chown mysql.mysql /data/logbin/
[root@centos7 ~]#systemctl start mariadb2.创建有复制权限的用户账号
[root@centos7 ~]#mysql
MariaDB [(none)]> grant replication slave on *.* to repluser@'192.168.45.%' identified by 'centos';
MariaDB [(none)]> show master logs;
+--------------+-----------+
| Log_name | File_size |
+--------------+-----------+
| mysql.000001 | 284 |
| mysql.000002 | 245 |
+--------------+-----------+3.主节点完整备份，并复制至从节点
[root@centos7 ~]#mysqldump -A -F --master-data=1 --single-transaction > /data/bak.sql
[root@centos7 ~]#scp /data/bak.sql 192.168.45.17:/data/
配置MySQL从节点
1.安装mariadb,修改配置文件
[root@centos7 ~]#yum install mariadb-server -y
[root@centos7 ~]#vim /etc/my.cnf
[mysqld]
server-id=17
read-only
innodb_file_per_table=1
...2.修改主节点备份文件
[root@centos7 ~]#vim /data/bak.sql
...
CHANGE MASTER TO
MASTER_HOST='192.168.45.7',
MASTER_USER='repluser',
MASTER_PASSWORD='centos',
MASTER_PORT=3306,
MASTER_LOG_FILE='mysql.000002',
MASTER_LOG_POS=245;
...3.导入主节点备份文件，开启slave
[root@centos7 ~]#systemctl start mariadb
[root@centos7 ~]#mysql < /data/bak.sql
[root@centos7 ~]#mysql
MariaDB [(none)]> start slave;
MariaDB [(none)]> show slave status\G
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.45.7Master_User: repluserMaster_Port: 3306Connect_Retry: 60Master_Log_File: mysql.000002Read_Master_Log_Pos: 245Relay_Log_File: mariadb-relay-bin.000002Relay_Log_Pos: 525Relay_Master_Log_File: mysql.000002Slave_IO_Running: YesSlave_SQL_Running: YesReplicate_Do_DB:Replicate_Ignore_DB:Replicate_Do_Table:Replicate_Ignore_Table:Replicate_Wild_Do_Table:Replicate_Wild_Ignore_Table:Last_Errno: 0Last_Error:Skip_Counter: 0Exec_Master_Log_Pos: 245Relay_Log_Space: 821Until_Condition: NoneUntil_Log_File:Until_Log_Pos: 0Master_SSL_Allowed: NoMaster_SSL_CA_File:Master_SSL_CA_Path:Master_SSL_Cert:Master_SSL_Cipher:Master_SSL_Key:Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: NoLast_IO_Errno: 0Last_IO_Error:Last_SQL_Errno: 0Last_SQL_Error:Replicate_Ignore_Server_Ids:Master_Server_Id: 7
测试MySQL主从同步
1.在主节点导入hellodb数据库
2.查看从节点是否正常同步
三、使用MHA实现Mysql高可用。
实验4台server：
管理节点：
MHA manager server 1台，ip：192.168.45.7
被管理节点：
mysql master server 1台，ip：192.168.45.17
mysql slave server 2台，ip：192.168.45.27 192.168.45.37
- 在管理节点上安装mha4mysql-manager和mha4mysql-node包
在被管理节点上安装mariadb-server和mha4mysql-node包 - 配置mysql主节点,并添加账户
[root@master ~]#vim /etc/my.cnf
[mysqld]
server-id=17
log-bin
skip_name_resolve=1
...
[root@master ~]#systemctl start mariadb
[root@master ~]#mysql
MariaDB [(none)]> grant replication slave on *.* to repluser@'192.168.45.%' identified by 'centos';
MariaDB [(none)]> grant all on *.* to mhauser@'192.168.45.%' identified by 'centos';
- 配置mysql从节点
1.配置从节点192.168.45.27
[root@slave27 ~]#vim /etc/my.cnf
[mysqld]
server-id=27
read-only
log-bin
relay_log_purge=0
skip_name_resolve=1
...
[root@slave27 ~]#systemctl start mariadb
[root@slave27 ~]#mysql
MariaDB [(none)]> CHANGE MASTER TO-> MASTER_HOST='192.168.45.17',-> MASTER_USER='repluser',-> MASTER_PASSWORD='centos',-> MASTER_PORT=3306,-> MASTER_LOG_FILE='mariadb-bin.000001',-> MASTER_LOG_POS=245;
MariaDB [(none)]> start slave;
MariaDB [(none)]> show slave status \G
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.45.17Master_User: repluserMaster_Port: 3306Connect_Retry: 60Master_Log_File: mariadb-bin.000001Read_Master_Log_Pos: 540Relay_Log_File: mariadb-relay-bin.000002Relay_Log_Pos: 826Relay_Master_Log_File: mariadb-bin.000001Slave_IO_Running: YesSlave_SQL_Running: Yes2.配置从节点192.168.45.37
[root@slave37 ~]#vim /etc/my.cnf
[mysqld]
server-id=37
read-only
log-bin
relay_log_purge=0
skip_name_resolve=1
...
[root@slave37 ~]#systemctl start mariadb
[root@slave37 ~]#mysql
MariaDB [(none)]>
MariaDB [(none)]>
MariaDB [(none)]> CHANGE MASTER TO-> MASTER_HOST='192.168.45.17',-> MASTER_USER='repluser',-> MASTER_PASSWORD='centos',-> MASTER_PORT=3306,-> MASTER_LOG_FILE='mariadb-bin.000001',-> MASTER_LOG_POS=245;
MariaDB [(none)]> start slave;
MariaDB [(none)]> show slave status \G
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.45.17Master_User: repluserMaster_Port: 3306Connect_Retry: 60Master_Log_File: mariadb-bin.000001Read_Master_Log_Pos: 540Relay_Log_File: mariadb-relay-bin.000002Relay_Log_Pos: 826Relay_Master_Log_File: mariadb-bin.000001Slave_IO_Running: YesSlave_SQL_Running: Yes
- 配置MHA管理节点
[root@mha-manager ~]#mkdir /etc/mha
[root@mha-manager ~]#vim /etc/mha/app1.cnf
[server default]
user=mhauser
password=centos
manager_workdir=/data/mastermha/app1/
manager_log=/data/mastermha/app1/manager.log
remote_workdir=/data/mastermha/app1/
ssh_user=root
repl_user=repluser
repl_password=centos
ping_interval=1[server1]
hostname=192.168.45.17
candidate_master=1 [server2]
hostname=192.168.45.27 [server3]
hostname=192.168.45.37
candidate_master=1
- 在所有节点实现相互之间ssh key验证
在管理节点上生成key，并将生成的key、公私钥拷贝到其余节点/root/.ssh文件夹中
[root@mha-manager ~]#ssh-keygen
[root@mha-manager ~]#ssh-copy-id 192.168.45.7
[root@mha-manager ~]#scp -r .ssh 192.168.45.17:/root/
[root@mha-manager ~]#scp -r .ssh 192.168.45.27:/root/
[root@mha-manager ~]#scp -r .ssh 192.168.45.37:/root/
- MHA验证和启动
[root@mha-manager ~]#masterha_check_ssh --conf=/etc/mha/app1.cnf
Fri Aug 7 15:20:18 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Fri Aug 7 15:20:18 2020 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:20:18 2020 - [info] Reading server configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:20:18 2020 - [info] Starting SSH connection tests..
Fri Aug 7 15:20:40 2020 - [debug]
Fri Aug 7 15:20:19 2020 - [debug] Connecting via SSH from root@192.168.45.27(192.168.45.27:22) to root@192.168.45.17(192.168.45.17:22)..
Fri Aug 7 15:20:29 2020 - [debug] ok.
Fri Aug 7 15:20:29 2020 - [debug] Connecting via SSH from root@192.168.45.27(192.168.45.27:22) to root@192.168.45.37(192.168.45.37:22)..
Fri Aug 7 15:20:40 2020 - [debug] ok.
Fri Aug 7 15:20:51 2020 - [debug]
Fri Aug 7 15:20:19 2020 - [debug] Connecting via SSH from root@192.168.45.37(192.168.45.37:22) to root@192.168.45.17(192.168.45.17:22)..
Fri Aug 7 15:20:30 2020 - [debug] ok.
Fri Aug 7 15:20:30 2020 - [debug] Connecting via SSH from root@192.168.45.37(192.168.45.37:22) to root@192.168.45.27(192.168.45.27:22)..
Fri Aug 7 15:20:50 2020 - [debug] ok.
Fri Aug 7 15:20:55 2020 - [debug]
Fri Aug 7 15:20:18 2020 - [debug] Connecting via SSH from root@192.168.45.17(192.168.45.17:22) to root@192.168.45.27(192.168.45.27:22)..
Fri Aug 7 15:20:34 2020 - [debug] ok.
Fri Aug 7 15:20:34 2020 - [debug] Connecting via SSH from root@192.168.45.17(192.168.45.17:22) to root@192.168.45.37(192.168.45.37:22)..
Fri Aug 7 15:20:54 2020 - [debug] ok.
Fri Aug 7 15:20:55 2020 - [info] All SSH connection tests passed successfully.[root@mha-manager ~]#masterha_check_repl --conf=/etc/mha/app1.cnf
Fri Aug 7 15:21:19 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Fri Aug 7 15:21:19 2020 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:21:19 2020 - [info] Reading server configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:21:19 2020 - [info] MHA::MasterMonitor version 0.56.
Creating directory /data/mastermha/app1/.. done.
Fri Aug 7 15:21:20 2020 - [info] GTID failover mode = 0
Fri Aug 7 15:21:20 2020 - [info] Dead Servers:
Fri Aug 7 15:21:20 2020 - [info] Alive Servers:
Fri Aug 7 15:21:20 2020 - [info] 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:21:20 2020 - [info] 192.168.45.27(192.168.45.27:3306)
Fri Aug 7 15:21:20 2020 - [info] 192.168.45.37(192.168.45.37:3306)
Fri Aug 7 15:21:20 2020 - [info] Alive Slaves:
Fri Aug 7 15:21:20 2020 - [info] 192.168.45.27(192.168.45.27:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:21:20 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:21:20 2020 - [info] 192.168.45.37(192.168.45.37:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:21:20 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:21:20 2020 - [info] Primary candidate for the new Master (candidate_master is set)
Fri Aug 7 15:21:20 2020 - [info] Current Alive Master: 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:21:20 2020 - [info] Checking slave configurations..
Fri Aug 7 15:21:20 2020 - [warning] relay_log_purge=0 is not set on slave 192.168.45.27(192.168.45.27:3306).
Fri Aug 7 15:21:20 2020 - [warning] relay_log_purge=0 is not set on slave 192.168.45.37(192.168.45.37:3306).
Fri Aug 7 15:21:20 2020 - [info] Checking replication filtering settings..
Fri Aug 7 15:21:20 2020 - [info] binlog_do_db= , binlog_ignore_db=
Fri Aug 7 15:21:20 2020 - [info] Replication filtering check ok.
Fri Aug 7 15:21:20 2020 - [info] GTID (with auto-pos) is not supported
Fri Aug 7 15:21:20 2020 - [info] Starting SSH connection tests..
Fri Aug 7 15:21:42 2020 - [info] All SSH connection tests passed successfully.
Fri Aug 7 15:21:42 2020 - [info] Checking MHA Node version..
Fri Aug 7 15:21:42 2020 - [info] Version check ok.
Fri Aug 7 15:21:42 2020 - [info] Checking SSH publickey authentication settings on the current master..
Fri Aug 7 15:21:43 2020 - [info] HealthCheck: SSH to 192.168.45.17 is reachable.
Fri Aug 7 15:21:43 2020 - [info] Master MHA Node version is 0.56.
Fri Aug 7 15:21:43 2020 - [info] Checking recovery script configurations on 192.168.45.17(192.168.45.17:3306)..
Fri Aug 7 15:21:43 2020 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/data/mastermha/app1//save_binary_logs_test --manager_version=0.56 --start_file=mariadb-bin.000001
Fri Aug 7 15:21:43 2020 - [info] Connecting to root@192.168.45.17(192.168.45.17:22)..Creating /data/mastermha/app1 if not exists.. Creating directory /data/mastermha/app1.. done.ok.Checking output directory is accessible or not..ok.Binlog found at /var/lib/mysql, up to mariadb-bin.000001
Fri Aug 7 15:21:43 2020 - [info] Binlog setting check done.
Fri Aug 7 15:21:43 2020 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Fri Aug 7 15:21:43 2020 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mhauser' --slave_host=192.168.45.27 --slave_ip=192.168.45.27 --slave_port=3306 --workdir=/data/mastermha/app1/ --target_version=5.5.65-MariaDB --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ --slave_pass=xxx
Fri Aug 7 15:21:43 2020 - [info] Connecting to root@192.168.45.27(192.168.45.27:22)..
Creating directory /data/mastermha/app1/.. done.Checking slave recovery environment settings..Opening /var/lib/mysql/relay-log.info ... ok.Relay log found at /var/lib/mysql, up to mariadb-relay-bin.000002Temporary relay log file is /var/lib/mysql/mariadb-relay-bin.000002Testing mysql connection and privileges.. done.Testing mysqlbinlog output.. done.Cleaning up test file(s).. done.
Fri Aug 7 15:21:43 2020 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mhauser' --slave_host=192.168.45.37 --slave_ip=192.168.45.37 --slave_port=3306 --workdir=/data/mastermha/app1/ --target_version=5.5.65-MariaDB --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ --slave_pass=xxx
Fri Aug 7 15:21:43 2020 - [info] Connecting to root@192.168.45.37(192.168.45.37:22)..
Creating directory /data/mastermha/app1/.. done.Checking slave recovery environment settings..Opening /var/lib/mysql/relay-log.info ... ok.Relay log found at /var/lib/mysql, up to mariadb-relay-bin.000002Temporary relay log file is /var/lib/mysql/mariadb-relay-bin.000002Testing mysql connection and privileges.. done.Testing mysqlbinlog output.. done.Cleaning up test file(s).. done.
Fri Aug 7 15:21:43 2020 - [info] Slaves settings check done.
Fri Aug 7 15:21:43 2020 - [info]
192.168.45.17(192.168.45.17:3306) (current master)+--192.168.45.27(192.168.45.27:3306)+--192.168.45.37(192.168.45.37:3306)Fri Aug 7 15:21:43 2020 - [info] Checking replication health on 192.168.45.27..
Fri Aug 7 15:21:43 2020 - [info] ok.
Fri Aug 7 15:21:43 2020 - [info] Checking replication health on 192.168.45.37..
Fri Aug 7 15:21:43 2020 - [info] ok.
Fri Aug 7 15:21:43 2020 - [warning] master_ip_failover_script is not defined.
Fri Aug 7 15:21:43 2020 - [warning] shutdown_script is not defined.
Fri Aug 7 15:21:43 2020 - [info] Got exit code 0 (Not master dead).MySQL Replication Health is OK.[root@mha-manager ~]#masterha_manager --conf=/etc/mha/app1.cnf
Fri Aug 7 15:23:01 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Fri Aug 7 15:23:01 2020 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:23:01 2020 - [info] Reading server configuration from /etc/mha/app1.cnf..
- 测试MHA高可用性
关闭mysql主节点mariadb服务
[root@master ~]#systemctl stop mariadb
从192.168.45.27上查看
MariaDB [(none)]> show slave status \G
*************************** 1. row ***************************Slave_IO_State: Waiting for master to send eventMaster_Host: 192.168.45.37Master_User: repluserMaster_Port: 3306Connect_Retry: 60Master_Log_File: mariadb-bin.000001Read_Master_Log_Pos: 245Relay_Log_File: mariadb-relay-bin.000002Relay_Log_Pos: 531Relay_Master_Log_File: mariadb-bin.000001Slave_IO_Running: YesSlave_SQL_Running: Yes
从管理节点的日志可以看到mysql主节点已经从192.168.45.17切换到192.168.45.37
[root@mha-manager ~]#tail -f /data/mastermha/app1/manager.log
192.168.45.17(192.168.45.17:3306) (current master)+--192.168.45.27(192.168.45.27:3306)+--192.168.45.37(192.168.45.37:3306)Fri Aug 7 15:23:21 2020 - [warning] master_ip_failover_script is not defined.
Fri Aug 7 15:23:21 2020 - [warning] shutdown_script is not defined.
Fri Aug 7 15:23:21 2020 - [info] Set master ping interval 1 seconds.
Fri Aug 7 15:23:21 2020 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
Fri Aug 7 15:23:21 2020 - [info] Starting ping health check on 192.168.45.17(192.168.45.17:3306)..
Fri Aug 7 15:23:21 2020 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..
Fri Aug 7 15:25:58 2020 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)
Fri Aug 7 15:25:58 2020 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/data/mastermha/app1//save_binary_logs_test --manager_version=0.56 --binlog_prefix=mariadb-bin
Fri Aug 7 15:25:59 2020 - [info] HealthCheck: SSH to 192.168.45.17 is reachable.
Fri Aug 7 15:25:59 2020 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.45.17' (111))
Fri Aug 7 15:25:59 2020 - [warning] Connection failed 2 time(s)..
Fri Aug 7 15:26:00 2020 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.45.17' (111))
Fri Aug 7 15:26:00 2020 - [warning] Connection failed 3 time(s)..
Fri Aug 7 15:26:01 2020 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.45.17' (111))
Fri Aug 7 15:26:01 2020 - [warning] Connection failed 4 time(s)..
Fri Aug 7 15:26:01 2020 - [warning] Master is not reachable from health checker!
Fri Aug 7 15:26:01 2020 - [warning] Master 192.168.45.17(192.168.45.17:3306) is not reachable!
Fri Aug 7 15:26:01 2020 - [warning] SSH is reachable.
Fri Aug 7 15:26:01 2020 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/mha/app1.cnf again, and trying to connect to all servers to check server status..
Fri Aug 7 15:26:01 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Fri Aug 7 15:26:01 2020 - [info] Reading application default configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:26:01 2020 - [info] Reading server configuration from /etc/mha/app1.cnf..
Fri Aug 7 15:26:02 2020 - [info] GTID failover mode = 0
Fri Aug 7 15:26:02 2020 - [info] Dead Servers:
Fri Aug 7 15:26:02 2020 - [info] 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:02 2020 - [info] Alive Servers:
Fri Aug 7 15:26:02 2020 - [info] 192.168.45.27(192.168.45.27:3306)
Fri Aug 7 15:26:02 2020 - [info] 192.168.45.37(192.168.45.37:3306)
Fri Aug 7 15:26:02 2020 - [info] Alive Slaves:
Fri Aug 7 15:26:02 2020 - [info] 192.168.45.27(192.168.45.27:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:02 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:02 2020 - [info] 192.168.45.37(192.168.45.37:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:02 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:02 2020 - [info] Primary candidate for the new Master (candidate_master is set)
Fri Aug 7 15:26:02 2020 - [info] Checking slave configurations..
Fri Aug 7 15:26:02 2020 - [warning] relay_log_purge=0 is not set on slave 192.168.45.27(192.168.45.27:3306).
Fri Aug 7 15:26:02 2020 - [warning] relay_log_purge=0 is not set on slave 192.168.45.37(192.168.45.37:3306).
Fri Aug 7 15:26:02 2020 - [info] Checking replication filtering settings..
Fri Aug 7 15:26:02 2020 - [info] Replication filtering check ok.
Fri Aug 7 15:26:02 2020 - [info] Master is down!
Fri Aug 7 15:26:02 2020 - [info] Terminating monitoring script.
Fri Aug 7 15:26:02 2020 - [info] Got exit code 20 (Master dead).
Fri Aug 7 15:26:02 2020 - [info] MHA::MasterFailover version 0.56.
Fri Aug 7 15:26:02 2020 - [info] Starting master failover.
Fri Aug 7 15:26:02 2020 - [info]
Fri Aug 7 15:26:02 2020 - [info] * Phase 1: Configuration Check Phase..
Fri Aug 7 15:26:02 2020 - [info]
Fri Aug 7 15:26:03 2020 - [info] GTID failover mode = 0
Fri Aug 7 15:26:03 2020 - [info] Dead Servers:
Fri Aug 7 15:26:03 2020 - [info] 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:03 2020 - [info] Checking master reachability via MySQL(double check)...
Fri Aug 7 15:26:03 2020 - [info] ok.
Fri Aug 7 15:26:03 2020 - [info] Alive Servers:
Fri Aug 7 15:26:03 2020 - [info] 192.168.45.27(192.168.45.27:3306)
Fri Aug 7 15:26:03 2020 - [info] 192.168.45.37(192.168.45.37:3306)
Fri Aug 7 15:26:03 2020 - [info] Alive Slaves:
Fri Aug 7 15:26:03 2020 - [info] 192.168.45.27(192.168.45.27:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:03 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:03 2020 - [info] 192.168.45.37(192.168.45.37:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:03 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:03 2020 - [info] Primary candidate for the new Master (candidate_master is set)
Fri Aug 7 15:26:03 2020 - [info] Starting Non-GTID based failover.
Fri Aug 7 15:26:03 2020 - [info]
Fri Aug 7 15:26:03 2020 - [info] ** Phase 1: Configuration Check Phase completed.
Fri Aug 7 15:26:03 2020 - [info]
Fri Aug 7 15:26:03 2020 - [info] * Phase 2: Dead Master Shutdown Phase..
Fri Aug 7 15:26:03 2020 - [info]
Fri Aug 7 15:26:03 2020 - [info] Forcing shutdown so that applications never connect to the current master..
Fri Aug 7 15:26:03 2020 - [warning] master_ip_failover_script is not set. Skipping invalidating dead master IP address.
Fri Aug 7 15:26:03 2020 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Fri Aug 7 15:26:04 2020 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Fri Aug 7 15:26:04 2020 - [info]
Fri Aug 7 15:26:04 2020 - [info] * Phase 3: Master Recovery Phase..
Fri Aug 7 15:26:04 2020 - [info]
Fri Aug 7 15:26:04 2020 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Fri Aug 7 15:26:04 2020 - [info]
Fri Aug 7 15:26:04 2020 - [info] The latest binary log file/position on all slaves is mariadb-bin.000001:540
Fri Aug 7 15:26:04 2020 - [info] Latest slaves (Slaves that received relay log files to the latest):
Fri Aug 7 15:26:04 2020 - [info] 192.168.45.27(192.168.45.27:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:04 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:04 2020 - [info] 192.168.45.37(192.168.45.37:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:04 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:04 2020 - [info] Primary candidate for the new Master (candidate_master is set)
Fri Aug 7 15:26:04 2020 - [info] The oldest binary log file/position on all slaves is mariadb-bin.000001:540
Fri Aug 7 15:26:04 2020 - [info] Oldest slaves:
Fri Aug 7 15:26:04 2020 - [info] 192.168.45.27(192.168.45.27:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:04 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:04 2020 - [info] 192.168.45.37(192.168.45.37:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:04 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:04 2020 - [info] Primary candidate for the new Master (candidate_master is set)
Fri Aug 7 15:26:04 2020 - [info]
Fri Aug 7 15:26:04 2020 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Fri Aug 7 15:26:04 2020 - [info]
Fri Aug 7 15:26:15 2020 - [info] Fetching dead master's binary logs..
Fri Aug 7 15:26:15 2020 - [info] Executing command on the dead master 192.168.45.17(192.168.45.17:3306): save_binary_logs --command=save --start_file=mariadb-bin.000001 --start_pos=540 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56Creating /data/mastermha/app1 if not exists.. ok.Concat binary/relay logs from mariadb-bin.000001 pos 540 to mariadb-bin.000001 EOF into /data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog ..Dumping binlog format description event, from position 0 to 245.. ok.Dumping effective binlog data from /var/lib/mysql/mariadb-bin.000001 position 540 to tail(559).. ok.Concat succeeded.
Fri Aug 7 15:26:15 2020 - [info] scp from root@192.168.45.17:/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog to local:/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog succeeded.
Fri Aug 7 15:26:15 2020 - [info] HealthCheck: SSH to 192.168.45.27 is reachable.
Fri Aug 7 15:26:16 2020 - [info] HealthCheck: SSH to 192.168.45.37 is reachable.
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] * Phase 3.3: Determining New Master Phase..
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Fri Aug 7 15:26:16 2020 - [info] All slaves received relay logs to the same position. No need to resync each other.
Fri Aug 7 15:26:16 2020 - [info] Searching new master from slaves..
Fri Aug 7 15:26:16 2020 - [info] Candidate masters from the configuration file:
Fri Aug 7 15:26:16 2020 - [info] 192.168.45.37(192.168.45.37:3306) Version=5.5.65-MariaDB (oldest major version between slaves) log-bin:enabled
Fri Aug 7 15:26:16 2020 - [info] Replicating from 192.168.45.17(192.168.45.17:3306)
Fri Aug 7 15:26:16 2020 - [info] Primary candidate for the new Master (candidate_master is set)
Fri Aug 7 15:26:16 2020 - [info] Non-candidate masters:
Fri Aug 7 15:26:16 2020 - [info] Searching from candidate_master slaves which have received the latest relay log events..
Fri Aug 7 15:26:16 2020 - [info] New master is 192.168.45.37(192.168.45.37:3306)
Fri Aug 7 15:26:16 2020 - [info] Starting master failover..
Fri Aug 7 15:26:16 2020 - [info]
From:
192.168.45.17(192.168.45.17:3306) (current master)+--192.168.45.27(192.168.45.27:3306)+--192.168.45.37(192.168.45.37:3306)To:
192.168.45.37(192.168.45.37:3306) (new master)+--192.168.45.27(192.168.45.27:3306)
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] * Phase 3.3: New Master Diff Log Generation Phase..
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Fri Aug 7 15:26:16 2020 - [info] Sending binlog..
Fri Aug 7 15:26:16 2020 - [info] scp from local:/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog to root@192.168.45.37:/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog succeeded.
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] * Phase 3.4: Master Log Apply Phase..
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Fri Aug 7 15:26:16 2020 - [info] Starting recovery on 192.168.45.37(192.168.45.37:3306)..
Fri Aug 7 15:26:16 2020 - [info] Generating diffs succeeded.
Fri Aug 7 15:26:16 2020 - [info] Waiting until all relay logs are applied.
Fri Aug 7 15:26:16 2020 - [info] done.
Fri Aug 7 15:26:16 2020 - [info] Getting slave status..
Fri Aug 7 15:26:16 2020 - [info] This slave(192.168.45.37)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mariadb-bin.000001:540). No need to recover from Exec_Master_Log_Pos.
Fri Aug 7 15:26:16 2020 - [info] Connecting to the target slave host 192.168.45.37, running recover script..
Fri Aug 7 15:26:16 2020 - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='mhauser' --slave_host=192.168.45.37 --slave_ip=192.168.45.37 --slave_port=3306 --apply_files=/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog --workdir=/data/mastermha/app1/ --target_version=5.5.65-MariaDB --timestamp=20200807152602 --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56 --slave_pass=xxx
Fri Aug 7 15:26:16 2020 - [info]
Applying differential binary/relay log files /data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog on 192.168.45.37:3306. This may take long time...
Applying log files succeeded.
Fri Aug 7 15:26:16 2020 - [info] All relay logs were successfully applied.
Fri Aug 7 15:26:16 2020 - [info] Getting new master's binlog name and position..
Fri Aug 7 15:26:16 2020 - [info] mariadb-bin.000001:245
Fri Aug 7 15:26:16 2020 - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.45.37', MASTER_PORT=3306, MASTER_LOG_FILE='mariadb-bin.000001', MASTER_LOG_POS=245, MASTER_USER='repluser', MASTER_PASSWORD='xxx';
Fri Aug 7 15:26:16 2020 - [warning] master_ip_failover_script is not set. Skipping taking over new master IP address.
Fri Aug 7 15:26:16 2020 - [info] Setting read_only=0 on 192.168.45.37(192.168.45.37:3306)..
Fri Aug 7 15:26:16 2020 - [info] ok.
Fri Aug 7 15:26:16 2020 - [info] ** Finished master recovery successfully.
Fri Aug 7 15:26:16 2020 - [info] * Phase 3: Master Recovery Phase completed.
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] * Phase 4: Slaves Recovery Phase..
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Fri Aug 7 15:26:16 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] -- Slave diff file generation on host 192.168.45.27(192.168.45.27:3306) started, pid: 23298. Check tmp log /data/mastermha/app1//192.168.45.27_3306_20200807152602.log if it takes time..
Fri Aug 7 15:26:17 2020 - [info]
Fri Aug 7 15:26:17 2020 - [info] Log messages from 192.168.45.27 ...
Fri Aug 7 15:26:17 2020 - [info]
Fri Aug 7 15:26:16 2020 - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Fri Aug 7 15:26:17 2020 - [info] End of log messages from 192.168.45.27.
Fri Aug 7 15:26:17 2020 - [info] -- 192.168.45.27(192.168.45.27:3306) has the latest relay log events.
Fri Aug 7 15:26:17 2020 - [info] Generating relay diff files from the latest slave succeeded.
Fri Aug 7 15:26:17 2020 - [info]
Fri Aug 7 15:26:17 2020 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Fri Aug 7 15:26:17 2020 - [info]
Fri Aug 7 15:26:17 2020 - [info] -- Slave recovery on host 192.168.45.27(192.168.45.27:3306) started, pid: 23306. Check tmp log /data/mastermha/app1//192.168.45.27_3306_20200807152602.log if it takes time..
Fri Aug 7 15:26:18 2020 - [info]
Fri Aug 7 15:26:18 2020 - [info] Log messages from 192.168.45.27 ...
Fri Aug 7 15:26:18 2020 - [info]
Fri Aug 7 15:26:17 2020 - [info] Sending binlog..
Fri Aug 7 15:26:18 2020 - [info] scp from local:/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog to root@192.168.45.27:/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog succeeded.
Fri Aug 7 15:26:18 2020 - [info] Starting recovery on 192.168.45.27(192.168.45.27:3306)..
Fri Aug 7 15:26:18 2020 - [info] Generating diffs succeeded.
Fri Aug 7 15:26:18 2020 - [info] Waiting until all relay logs are applied.
Fri Aug 7 15:26:18 2020 - [info] done.
Fri Aug 7 15:26:18 2020 - [info] Getting slave status..
Fri Aug 7 15:26:18 2020 - [info] This slave(192.168.45.27)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mariadb-bin.000001:540). No need to recover from Exec_Master_Log_Pos.
Fri Aug 7 15:26:18 2020 - [info] Connecting to the target slave host 192.168.45.27, running recover script..
Fri Aug 7 15:26:18 2020 - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='mhauser' --slave_host=192.168.45.27 --slave_ip=192.168.45.27 --slave_port=3306 --apply_files=/data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog --workdir=/data/mastermha/app1/ --target_version=5.5.65-MariaDB --timestamp=20200807152602 --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.56 --slave_pass=xxx
Fri Aug 7 15:26:18 2020 - [info]
Applying differential binary/relay log files /data/mastermha/app1//saved_master_binlog_from_192.168.45.17_3306_20200807152602.binlog on 192.168.45.27:3306. This may take long time...
Applying log files succeeded.
Fri Aug 7 15:26:18 2020 - [info] All relay logs were successfully applied.
Fri Aug 7 15:26:18 2020 - [info] Resetting slave 192.168.45.27(192.168.45.27:3306) and starting replication from the new master 192.168.45.37(192.168.45.37:3306)..
Fri Aug 7 15:26:18 2020 - [info] Executed CHANGE MASTER.
Fri Aug 7 15:26:18 2020 - [info] Slave started.
Fri Aug 7 15:26:18 2020 - [info] End of log messages from 192.168.45.27.
Fri Aug 7 15:26:18 2020 - [info] -- Slave recovery on host 192.168.45.27(192.168.45.27:3306) succeeded.
Fri Aug 7 15:26:18 2020 - [info] All new slave servers recovered successfully.
Fri Aug 7 15:26:18 2020 - [info]
Fri Aug 7 15:26:18 2020 - [info] * Phase 5: New master cleanup phase..
Fri Aug 7 15:26:18 2020 - [info]
Fri Aug 7 15:26:18 2020 - [info] Resetting slave info on the new master..
Fri Aug 7 15:26:18 2020 - [info] 192.168.45.37: Resetting slave info succeeded.
Fri Aug 7 15:26:18 2020 - [info] Master failover to 192.168.45.37(192.168.45.37:3306) completed successfully.
Fri Aug 7 15:26:18 2020 - [info]----- Failover Report -----app1: MySQL Master failover 192.168.45.17(192.168.45.17:3306) to 192.168.45.37(192.168.45.37:3306) succeededMaster 192.168.45.17(192.168.45.17:3306) is down!Check MHA Manager logs at mha-manager:/data/mastermha/app1/manager.log for details.Started automated(non-interactive) failover.
The latest slave 192.168.45.27(192.168.45.27:3306) has all relay logs for recovery.
Selected 192.168.45.37(192.168.45.37:3306) as a new master.
192.168.45.37(192.168.45.37:3306): OK: Applying all logs succeeded.
192.168.45.27(192.168.45.27:3306): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
192.168.45.27(192.168.45.27:3306): OK: Applying all logs succeeded. Slave started, replicating from 192.168.45.37(192.168.45.37:3306)
192.168.45.37(192.168.45.37:3306): Resetting slave info succeeded.
Master failover to 192.168.45.37(192.168.45.37:3306) completed successfully.
如若内容造成侵权/违法违规/事实不符，请联系编程学习网邮箱：809451989@qq.com进行投诉反馈，一经查实，立即删除！
相关文章
- CCF 201909-1 小明种苹果 （C++）
201909-1 小明种苹果 试题编号： 201909-1 试题名称： 小明种苹果 时间限制： 2.0s 内存限制： 512.0MB 问题描述：解题过程 按照题意直接求解即可，这里采用结构体排序的方法得出最终结果。AC代码 #include<iostream> #include<algorithm> using namespace std; s…...
2024/5/1 9:07:34 - Qt利用EasyPr实现车牌识别简单上位机界面(含雷达扫描)
对于Qt实现的easyPr项目，网上能找的现成不是很多，所以特意做了个小界面。easypr这个开源项目可以在git上找到，但是目前好像不怎么维护了。在使用这个项目的时候自己一定要配置好Opencv的环境，然后按照自己的路径更改一下pro文件下的路径，基本就可以编译实现了。识别结果的…...
2024/4/30 22:43:59 - 有限公司利用核定征收政策可以减少哪些税负压力？
纳税缴税是每个公民的义务，我国繁重的税负压力对公司的影响颇大，特别是处于刚成立没多久的公司来说，税负压力严重阻碍了发展空间，对于这种情况不少公司和个人都在考虑税务上的筹划，在筹划上就必须需要遵循合理合法合规的原则。 目前个人独资企业核定征收就是在节税上面来说…...
2024/5/1 16:54:21 - Android中 RelativeLayout 各个属性的用法
android:layout_above="@id/xxx" --将控件置于给定ID控件之上 android:layout_below="@id/xxx" --将控件置于给定ID控件之下 android:layout_toLeftOf="@id/xxx" --将控件的右边缘和给定ID控件的左边缘对齐 android:layout_toRightOf="@id/…...
2024/5/1 13:21:33 - LeetCode-回文对
字典树写法：class Solution {//使用字典树（也叫前缀树）来解决此问题//首先构建字典树，实现insert和search方法class Node{//表示字母在字典树中的索引int[] pos = new int[26];//flag表示当前字符串对应的words中的索引int flag;public Node(){flag = -1;}}//创建一棵字典树…...
2024/5/1 10:31:46 - LeetCode刷题(0002)---677. 键值映射，python3
目录LeetCode---677. 键值映射，python301题目描述：02题目分析：重点理解 ：同时获取key和value使用的item()函数获取到元组，然后拆包！03解答：04运行结果：1.时间运行图：2.内存使用情况05结语： LeetCode—677. 键值映射，python3 01题目描述： 实现一个 MapSum 类里的两个…...
2024/4/22 14:40:58 - chipyard的toolchain安装出错1
chipyard安装步骤见官网https://chipyard.readthedocs.io/en/latest/Simulation/Software-RTL-Simulation.html#synopsys-vcs-license-required我是在执行这条命令时出了错：./scripts/build-toolchains.sh riscv-tools # for a normal risc-v toolchain错误见图：unable to ac…...
2024/5/1 8:52:35 - lora组网的几种模式
lora技术应用在很多场景，比如：隧道通讯，电网监测，电表、水表等表类数据采集，智慧农业， 智慧水利，智慧交通，智慧社区，环境监测，工业自动化检测，水产养殖等。有如下几种工作模式。 1、点对点2、星型3、级联 级联时，设备相对于一个中继器，将数据转发出去，实现超长距…...
2024/5/1 7:54:51 - 币圈暴涨暴跌有这五大技巧就够了
币圈市场各大消息面往往伴随着大行情到来，币圈交易毕竟不是赌博，需要清晰的思路，在这总结下币圈投资五大做单技巧，希望能对大家有所帮助。 第一招：认识趋势 顺势而为是任何投资理财的制胜法宝，所以第一招就是“认识趋势”。趋势是一个中长期的概念，代表着一个较长时间内…...
2024/4/20 14:54:56 - Error interpreting the template of the input: template: text:3:22: executing “text“ at ＜.paths＞
使用filebeat 的 module 监控kakfa log，启动filebeat报错：Error interpreting the template of the input: template: text:3:22: executing "text" at <.paths>: range cant iterate over /var/log/kafka/server.log报错是filebeat.yml 文件中指定路径的写法…...
2024/4/15 13:25:29 - 小小感悟
最近发现知识很不够用啦！ 在做系统时发现一个小系统维护起来都很困难，尤其是接手别人的系统，简直要崩溃，唉😔 慢慢来吧 接下来想学习一下vue和算法...
2024/4/15 13:25:32 - Oracle的row_number函数的使用
Oracle提供的row_number（）函数可以实现加rownum的作用，并且可以根据字段值的分类，在同类中进行排序SELECT id,NAME,class_id,score，row_number() OVER (PARTITION BY class_id ORDER BY score DESC ) FROM STUDENT将学生表中将每个年级的学生成绩进行排名其中PARTITION BY…...
2024/4/17 4:38:44 - 2020-0807-背包问题九讲（待完善）
代码和思想：来源于大雪菜 网站：https://www.acwing.com/about/ 遍历物品 -> 遍历约束条件 -> 遍历决策 01背包问题 每一个物品只能选一个，或者不选，求不超出容量的物品的最大价值。 二维dp，遍历约束（体积），是什么顺序就无所谓了。 import java.util.*; public cl…...
2024/4/23 19:54:47 - spring-boot学习：十三、spring-boot统一异常处理
上文讲了如何对返回的数据格式进行统一处理，本文主要是进一步对异常情况的补充。 在后台接口处理的过程中会产生各种各样的异常，比如参数校验异常、系统内部异常、业务逻辑异常等，这些异常产生在各个环节，不能随意抛给调用方，格式不一致会导致调用方无法处理。 实现思路：…...
2024/4/22 8:24:21 - 2020 8.7 暑期线段树专题
线段树可以在 n*logn 的时间复杂度内实现单点修改、区间 修改、区间查询（区间求和，求区间最大值，求区间最小值） 等操作。在这里顺便把树状数组附上，树状数组只能区间求和时间复杂度也是n*log ncode:#include <cstdio> #include <cstring> #include <iostre…...
2024/4/28 20:39:51 - 剑指 Offer 27. 二叉树的镜像
题目描述思路分析 递归进行左右子树的互换即可 代码展示 /*** Definition for a binary tree node.* struct TreeNode {* int val;* TreeNode *left;* TreeNode *right;* TreeNode(int x) : val(x), left(NULL), right(NULL) {}* };*/ class Solution { public…...
2024/4/15 13:25:23 - hive的UDF函数实现
hive的UDF函数的实现步骤:1.自定义一个实现类继承UDF,重写evaluate方法(自己想要实现的功能)2.把上面的类打成jar包上传到服务器以及hdfs中3.在使用hive语句时可以直接调用我们的方法即可参考博客:https://blog.csdn.net/zmywei_20160707/article/details/81698542...
2024/4/15 13:25:24 - Mysql 索引使用规则和设计优化
大部分情况下，尤其是记录数量较少的情况下Mysql总是能正常运转的很好，但不可避免的，随着数据库记录数的增长以及SQL语句越来越复杂，总会有一些实际效果与数据库或SQL设计人员理解相违背的情况，这就需要开发者对Mysql的原理和存在的问题有一个基本的认识。本文主要探讨了My…...
2024/4/27 8:49:08 - shiro登录、权限步骤
shiro 登录 /*** 登录* @param userName* @param password* @return*/@RequestMapping(value = "/login",method = RequestMethod.POST)public Result login(String userName, String password) {System.out.println("---------------------------------------…...
2024/4/15 20:46:15 - linux运维基础[日志管理]——————chronyd时间同步、timedatectl设置系统时间、journal日志采集
文章目录1.时间同步服务1.1 服务端1.2 在客户端1.3 测试2.设置系统时间3.新的日志采集方式journal3.1 journalctl 日志查看工具3.2 存放journal采集的日志 1.时间同步服务 我们在进行日志管理的时候，需要客户端的时间与服务器端相同。 chronyd是一个同步系统时钟的守护进程。 …...
2024/4/20 22:43:36
最新文章
- C++笔试练习笔记 【2】： 数字统计 BC153 两个数组的交集 NC313 点击消除 AB5
文章目录 数字统计分析题目代码部分 两个数组的交集题目分析代码部分 点击消除题目解析代码部分 数字统计 分析题目 这个题涉及到两个知识点，就是枚举和数字的拆分 那么我的思路是进行遍历，拆分数字判断二的个数，枚举进行计数 那么数字的拆分…...
2024/5/1 18:15:35 - 梯度消失和梯度爆炸的一些处理方法
在这里是记录一下梯度消失或梯度爆炸的一些处理技巧。全当学习总结了如有错误还请留言，在此感激不尽。 权重和梯度的更新公式如下： w w − η ⋅ ∇ w w w - \eta \cdot \nabla w ww−η⋅∇w 个人通俗的理解梯度消失就是网络模型在反向求导的时候出…...
2024/3/20 10:50:27 - EasyExcel 校验后导入
引入pom <dependency><groupId>com.alibaba</groupId><artifactId>easyexcel</artifactId><version>3.3.3</version></dependency>触发校验类 import com.baomidou.mybatisplus.extension.api.R; import lombok.experimental…...
2024/4/30 2:06:43 - 腾讯云容器与Serverless的融合：探索《2023技术实践精选集》中的创新实践
腾讯云容器与Serverless的融合：探索《2023技术实践精选集》中的创新实践 文章目录 腾讯云容器与Serverless的融合：探索《2023技术实践精选集》中的创新实践引言《2023腾讯云容器和函数计算技术实践精选集》整体评价特色亮点分析Serverless与Kubernetes的…...
2024/4/30 17:11:00 - 2024免费Mac苹果解压压缩包软件BetterZip5
在2024年，对于Mac电脑用户来说，如果你想要无需解压就能快速查看压缩文档的内容，BetterZip是一个极佳的选择。这款软件不仅支持多种格式的压缩和解压，如zip、rar、7z、tar等，还具备丰富的功能和设置，包括预览…...
2024/4/30 17:23:46 - 416. 分割等和子集问题（动态规划）
题目 题解 class Solution:def canPartition(self, nums: List[int]) -> bool:# badcaseif not nums:return True# 不能被2整除if sum(nums) % 2 ! 0:return False# 状态定义：dp[i][j]表示当背包容量为j，用前i个物品是否正好可以将背包填满ÿ…...
2024/5/1 10:25:26 - 【Java】ExcelWriter自适应宽度工具类（支持中文）
工具类 import org.apache.poi.ss.usermodel.Cell; import org.apache.poi.ss.usermodel.CellType; import org.apache.poi.ss.usermodel.Row; import org.apache.poi.ss.usermodel.Sheet;/*** Excel工具类** author xiaoming* date 2023/11/17 10:40*/ public class ExcelUti…...
2024/5/1 13:20:04 - Spring cloud负载均衡@LoadBalanced LoadBalancerClient
LoadBalance vs Ribbon 由于Spring cloud2020之后移除了Ribbon，直接使用Spring Cloud LoadBalancer作为客户端负载均衡组件，我们讨论Spring负载均衡以Spring Cloud2020之后版本为主，学习Spring Cloud LoadBalance，暂不讨论Ribbon…...
2024/4/29 18:43:42 - TSINGSEE青犀AI智能分析+视频监控工业园区周界安全防范方案
一、背景需求分析 在工业产业园、化工园或生产制造园区中，周界防范意义重大，对园区的安全起到重要的作用。常规的安防方式是采用人员巡查，人力投入成本大而且效率低。周界一旦被破坏或入侵，会影响园区人员和资产安全，…...
2024/5/1 4:07:45 - VB.net WebBrowser网页元素抓取分析方法
在用WebBrowser编程实现网页操作自动化时，常要分析网页Html，例如网页在加载数据时，常会显示“系统处理中，请稍候..”，我们需要在数据加载完成后才能继续下一步操作，如何抓取这个信息的网页html元素变化&…...
2024/4/30 23:32:22 - 【Objective-C】Objective-C汇总
方法定义 参考：https://www.yiibai.com/objective_c/objective_c_functions.html Objective-C编程语言中方法定义的一般形式如下 - (return_type) method_name:( argumentType1 )argumentName1 joiningArgument2:( argumentType2 )argumentName2 ... joiningArgu…...
2024/4/30 23:16:16 - 【洛谷算法题】P5713-洛谷团队系统【入门2分支结构】
👨💻博客主页：花无缺 欢迎 点赞👍 收藏⭐ 留言📝 加关注✅! 本文由 花无缺 原创 收录于专栏 【洛谷算法题】 文章目录 【洛谷算法题】P5713-洛谷团队系统【入门2分支结构】🌏题目描述🌏输入格…...
2024/5/1 6:35:25 - 【ES6.0】- 扩展运算符（...）
【ES6.0】- 扩展运算符... 文章目录 【ES6.0】- 扩展运算符...一、概述二、拷贝数组对象三、合并操作四、参数传递五、数组去重六、字符串转字符数组七、NodeList转数组八、解构变量九、打印日志十、总结 一、概述 **扩展运算符(...)**允许一个表达式在期望多个参数࿰…...
2024/5/1 11:24:00 - 摩根看好的前智能硬件头部品牌双11交易数据极度异常！——是模式创新还是饮鸩止渴？
文 | 螳螂观察 作者 | 李燃 双11狂欢已落下帷幕，各大品牌纷纷晒出优异的成绩单，摩根士丹利投资的智能硬件头部品牌凯迪仕也不例外。然而有爆料称，在自媒体平台发布霸榜各大榜单喜讯的凯迪仕智能锁，多个平台数据都表现出极度异常…...
2024/5/1 4:35:02 - Go语言常用命令详解(二)
文章目录 前言常用命令go bug示例参数说明 go doc示例参数说明 go env示例 go fix示例 go fmt示例 go generate示例 总结写在最后 前言 接着上一篇继续介绍Go语言的常用命令 常用命令 以下是一些常用的Go命令，这些命令可以帮助您在Go开发中进行编译、测试、运行和…...
2024/4/30 14:53:47 - 用欧拉路径判断图同构推出reverse合法性：1116T4
http://cplusoj.com/d/senior/p/SS231116D 假设我们要把 a a a 变成 b b b，我们在 a i a_i ai 和 a i 1 a_{i1} ai1 之间连边， b b b 同理，则 a a a 能变成 b b b 的充要条件是两图 A , B A,B A,B 同构。 必要性显然࿰…...
2024/4/30 22:14:26 - 【NGINX--1】基础知识
1、在 Debian/Ubuntu 上安装 NGINX 在 Debian 或 Ubuntu 机器上安装 NGINX 开源版。 更新已配置源的软件包信息，并安装一些有助于配置官方 NGINX 软件包仓库的软件包： apt-get update apt install -y curl gnupg2 ca-certificates lsb-release debian-…...
2024/5/1 6:34:45 - Hive默认分割符、存储格式与数据压缩
目录 1、Hive默认分割符2、Hive存储格式3、Hive数据压缩 1、Hive默认分割符 Hive创建表时指定的行受限（ROW FORMAT）配置标准HQL为： ... ROW FORMAT DELIMITED FIELDS TERMINATED BY \u0001 COLLECTION ITEMS TERMINATED BY , MAP KEYS TERMI…...
2024/4/30 22:57:18 - 【论文阅读】MAG：一种用于航天器遥测数据中有效异常检测的新方法
文章目录 摘要1 引言2 问题描述3 拟议框架4 所提出方法的细节A.数据预处理B.变量相关分析C.MAG模型D.异常分数 5 实验A.数据集和性能指标B.实验设置与平台C.结果和比较 6 结论 摘要 异常检测是保证航天器稳定性的关键。在航天器运行过程中，传感器和控制器产生大量周…...
2024/4/30 20:39:53 - --max-old-space-size=8192报错
vue项目运行时，如果经常运行慢，崩溃停止服务，报如下错误 FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory 因为在 Node 中，通过JavaScript使用内存时只能使用部分内存（64位系统&…...
2024/5/1 4:45:02 - 基于深度学习的恶意软件检测
恶意软件是指恶意软件犯罪者用来感染个人计算机或整个组织的网络的软件。 它利用目标系统漏洞，例如可以被劫持的合法软件（例如浏览器或 Web 应用程序插件）中的错误。 恶意软件渗透可能会造成灾难性的后果，包括数据被盗、勒索或网…...
2024/5/1 8:32:56 - JS原型对象prototype
让我简单的为大家介绍一下原型对象prototype吧！ 使用原型实现方法共享 1.构造函数通过原型分配的函数是所有对象所 共享的。 2.JavaScript 规定，每一个构造函数都有一个 prototype 属性，指向另一个对象，所以我们也称为原型对象…...
2024/5/1 14:33:22 - C++中只能有一个实例的单例类
C中只能有一个实例的单例类 前面讨论的 President 类很不错，但存在一个缺陷：无法禁止通过实例化多个对象来创建多名总统： President One, Two, Three; 由于复制构造函数是私有的，其中每个对象都是不可复制的，但您的目…...
2024/5/1 11:51:23 - python django 小程序图书借阅源码
开发工具： PyCharm，mysql5.7，微信开发者工具 技术说明： python django html 小程序 功能介绍： 用户端： 登录注册（含授权登录） 首页显示搜索图书，轮播图࿰…...
2024/5/1 5:23:20 - 电子学会C/C++编程等级考试2022年03月（一级）真题解析
C/C++等级考试（1~8级）全部真题・点这里 第1题：双精度浮点数的输入输出 输入一个双精度浮点数，保留8位小数，输出这个浮点数。 时间限制：1000 内存限制：65536输入 只有一行，一个双精度浮点数。输出 一行，保留8位小数的浮点数。样例输入 3.1415926535798932样例输出 3.1…...
2024/4/30 20:52:33 - 配置失败还原请勿关闭计算机,电脑开机屏幕上面显示，配置失败还原更改 请勿关闭计算机 开不了机 这个问题怎么办...
解析如下：1、长按电脑电源键直至关机，然后再按一次电源健重启电脑，按F8健进入安全模式2、安全模式下进入Windows系统桌面后，按住“winR”打开运行窗口，输入“services.msc”打开服务设置3、在服务界面，选中…...
2022/11/19 21:17:18 - 错误使用 reshape要执行 RESHAPE，请勿更改元素数目。
%读入6幅图像（每一幅图像的大小是564*564） f1 imread(WashingtonDC_Band1_564.tif); subplot(3,2,1),imshow(f1); f2 imread(WashingtonDC_Band2_564.tif); subplot(3,2,2),imshow(f2); f3 imread(WashingtonDC_Band3_564.tif); subplot(3,2,3),imsho…...
2022/11/19 21:17:16 - 配置 已完成 请勿关闭计算机,win7系统关机提示“配置Windows Update已完成30%请勿关闭计算机...
win7系统关机提示“配置Windows Update已完成30%请勿关闭计算机”问题的解决方法在win7系统关机时如果有升级系统的或者其他需要会直接进入一个 等待界面，在等待界面中我们需要等待操作结束才能关机，虽然这比较麻烦，但是对系统进行配置和升级…...
2022/11/19 21:17:15 - 台式电脑显示配置100%请勿关闭计算机,“准备配置windows 请勿关闭计算机”的解决方法...
有不少用户在重装Win7系统或更新系统后会遇到“准备配置windows，请勿关闭计算机”的提示，要过很久才能进入系统，有的用户甚至几个小时也无法进入，下面就教大家这个问题的解决方法。第一种方法：我们首先在左下角的“开始…...
2022/11/19 21:17:14 - win7 正在配置 请勿关闭计算机,怎么办Win7开机显示正在配置Windows Update请勿关机...
置信有很多用户都跟小编一样遇到过这样的问题，电脑时发现开机屏幕显现“正在配置Windows Update，请勿关机”(如下图所示)，而且还需求等大约5分钟才干进入系统。这是怎样回事呢？一切都是正常操作的，为什么开时机呈现“正…...
2022/11/19 21:17:13 - 准备配置windows 请勿关闭计算机 蓝屏,Win7开机总是出现提示“配置Windows请勿关机”...
Win7系统开机启动时总是出现“配置Windows请勿关机”的提示，没过几秒后电脑自动重启，每次开机都这样无法进入系统，此时碰到这种现象的用户就可以使用以下5种方法解决问题。方法一：开机按下F8，在出现的Windows高级启动选…...
2022/11/19 21:17:12 - 准备windows请勿关闭计算机要多久,windows10系统提示正在准备windows请勿关闭计算机怎么办...
有不少windows10系统用户反映说碰到这样一个情况，就是电脑提示正在准备windows请勿关闭计算机，碰到这样的问题该怎么解决呢，现在小编就给大家分享一下windows10系统提示正在准备windows请勿关闭计算机的具体第一种方法：1、2、依次…...
2022/11/19 21:17:11 - 配置 已完成 请勿关闭计算机,win7系统关机提示“配置Windows Update已完成30%请勿关闭计算机”的解决方法...
今天和大家分享一下win7系统重装了Win7旗舰版系统后，每次关机的时候桌面上都会显示一个“配置Windows Update的界面，提示请勿关闭计算机”，每次停留好几分钟才能正常关机，导致什么情况引起的呢？出现配置Windows Update…...
2022/11/19 21:17:10 - 电脑桌面一直是清理请关闭计算机,windows7一直卡在清理 请勿关闭计算机-win7清理请勿关机,win7配置更新35%不动...
只能是等着，别无他法。说是卡着如果你看硬盘灯应该在读写。如果从 Win 10 无法正常回滚，只能是考虑备份数据后重装系统了。解决来方案一：管理员运行cmd：net stop WuAuServcd %windir%ren SoftwareDistribution SDoldnet start WuA…...
2022/11/19 21:17:09 - 计算机配置更新不起,电脑提示“配置Windows Update请勿关闭计算机”怎么办？
原标题：电脑提示“配置Windows Update请勿关闭计算机”怎么办？win7系统中在开机与关闭的时候总是显示“配置windows update请勿关闭计算机”相信有不少朋友都曾遇到过一次两次还能忍但经常遇到就叫人感到心烦了遇到这种问题怎么办呢？一般的方…...
2022/11/19 21:17:08 - 计算机正在配置无法关机,关机提示 windows7 正在配置windows 请勿关闭计算机 ，然后等了一晚上也没有关掉。现在电脑无法正常关机...
关机提示 windows7 正在配置windows 请勿关闭计算机 ，然后等了一晚上也没有关掉。现在电脑无法正常关机以下文字资料是由(历史新知网www.lishixinzhi.com)小编为大家搜集整理后发布的内容，让我们赶快一起来看一下吧！关机提示 windows7 正在配…...
2022/11/19 21:17:05 - 钉钉提示请勿通过开发者调试模式_钉钉请勿通过开发者调试模式是真的吗好不好用...
钉钉请勿通过开发者调试模式是真的吗好不好用 更新时间：2020-04-20 22:24:19 浏览次数：729次 区域： 南阳 > 卧龙 列举网提醒您：为保障您的权益，请不要提前支付任何费用！ 虚拟位置外设器!!轨迹模拟&虚拟位置外设神器 专业用于：钉钉，外勤365，红圈通，企业微信和…...
2022/11/19 21:17:05 - 配置失败还原请勿关闭计算机怎么办,win7系统出现“配置windows update失败 还原更改 请勿关闭计算机”，长时间没反应，无法进入系统的解决方案...
前几天班里有位学生电脑(windows 7系统)出问题了，具体表现是开机时一直停留在“配置windows update失败 还原更改 请勿关闭计算机”这个界面，长时间没反应，无法进入系统。这个问题原来帮其他同学也解决过，网上搜了不少资料&#x…...
2022/11/19 21:17:04 - 一个电脑无法关闭计算机你应该怎么办,电脑显示“清理请勿关闭计算机”怎么办？...
本文为你提供了3个有效解决电脑显示“清理请勿关闭计算机”问题的方法，并在最后教给你1种保护系统安全的好方法，一起来看看！电脑出现“清理请勿关闭计算机”在Windows 7(SP1)和Windows Server 2008 R2 SP1中，添加了1个新功能在“磁…...
2022/11/19 21:17:03 - 请勿关闭计算机还原更改要多久,电脑显示:配置windows更新失败，正在还原更改，请勿关闭计算机怎么办...
许多用户在长期不使用电脑的时候，开启电脑发现电脑显示：配置windows更新失败，正在还原更改，请勿关闭计算机。。.这要怎么办呢？下面小编就带着大家一起看看吧！如果能够正常进入系统，建议您暂时移…...
2022/11/19 21:17:02 - 还原更改请勿关闭计算机 要多久,配置windows update失败 还原更改 请勿关闭计算机，电脑开机后一直显示以...
配置windows update失败 还原更改 请勿关闭计算机，电脑开机后一直显示以以下文字资料是由(历史新知网www.lishixinzhi.com)小编为大家搜集整理后发布的内容，让我们赶快一起来看一下吧！配置windows update失败 还原更改 请勿关闭计算机&#x…...
2022/11/19 21:17:01 - 电脑配置中请勿关闭计算机怎么办,准备配置windows请勿关闭计算机一直显示怎么办【图解】...
不知道大家有没有遇到过这样的一个问题，就是我们的win7系统在关机的时候，总是喜欢显示“准备配置windows，请勿关机”这样的一个页面，没有什么大碍，但是如果一直等着的话就要两个小时甚至更久都关不了机，非常…...
2022/11/19 21:17:00 - 正在准备配置请勿关闭计算机,正在准备配置windows请勿关闭计算机时间长了解决教程...
当电脑出现正在准备配置windows请勿关闭计算机时，一般是您正对windows进行升级，但是这个要是长时间没有反应，我们不能再傻等下去了。可能是电脑出了别的问题了，来看看教程的说法。正在准备配置windows请勿关闭计算机时间长了方法一…...
2022/11/19 21:16:59 - 配置失败还原请勿关闭计算机,配置Windows Update失败，还原更改请勿关闭计算机...
我们使用电脑的过程中有时会遇到这种情况，当我们打开电脑之后，发现一直停留在一个界面：“配置Windows Update失败，还原更改请勿关闭计算机”，等了许久还是无法进入系统。如果我们遇到此类问题应该如何解决呢࿰…...
2022/11/19 21:16:58 - 如何在iPhone上关闭“请勿打扰”
Apple’s “Do Not Disturb While Driving” is a potentially lifesaving iPhone feature, but it doesn’t always turn on automatically at the appropriate time. For example, you might be a passenger in a moving car, but your iPhone may think you’re the one dri…...
2022/11/19 21:16:57