Percona Server 5.6 Master-Slave Replication测试

最新推荐文章于 2024-09-30 17:19:22 发布
最新推荐文章于 2024-09-30 17:19:22 发布
阅读量95 收藏
点赞数
文章标签： 数据库 网络 操作系统
原文链接：https://my.oschina.net/boltwu/blog/719838
版权

为什么80%的码农都做不了架构师？>>>   hot3.png

MySQL的Master-Slave Replication是一个异步的复制过程，从一个 MySQL instance(Master)复制到另一个 instance(Slave)。在Master与Slave之间的实现整个复制过程主要由三个线程来完成，其中两个线程(SQL线程和IO线程)在 Slave 端，另外一个线程(IO线程)在Master端。 在MySQL Multi-Master兴起的今天，Master-Slave依然有着不少应用场景。
MySQL 复制的基本过程如下（http://machael.blog.51cto.com/829462/239112/）：
1. Slave上面的IO线程连接上 Master，并请求从指定日志文件的指定位置(或者从最开始的日志)之后的日志内容;
2. Master 接收到来自 Slave 的 IO 线程的请求后，通过负责复制的 IO 线程根据请求信息读取指定日志指定位置之后的日志信息，返回给 Slave 端的 IO 线程。返回信息中除了日志所包含的信息之外，还包括本次返回的信息在 Master 端的 Binary Log 文件的名称以及在 Binary Log 中的位置;
3. Slave 的 IO 线程接收到信息后，将接收到的日志内容依次写入到 Slave 端的Relay Log文件(mysql-relay-bin.xxxxxx)的最末端，并将读取到的Master端的bin-log的文件名和位置记录到master-
info文件中，以便在下一次读取的时候能够清楚的高速Master“我需要从某个bin-log的哪个位置开始往后的日志内容，请发给我”
​4. Slave 的 SQL 线程检测到 Relay Log 中新增加了内容后，会马上解析该 Log 文件中的内容成为在 Master 端真实执行时候的那些可执行的 Query 语句，并在自身执行这些 Query。这样，实际上就是在 Master 端和 Slave 端执行了同样的 Query，所以两端的数据是完全一样的。
下面就在CentOS 6.5 两节点的环境中配置一个简单的Percona Server 5.6.16 Master-Slave复制：
OStack01 ​192.168.46.132
OStack02 ​192.168.46.133

1. 安装Percona

在Master, Slave安装Percona Server

[root@localhost Desktop]# rpm -ivh http://www.percona.com/downloads/Percona-Server-5.6/LATEST/binary/redhat/6/x86_64/Percona-Server-shared-56-5.6.16-rel64.2.el6.x86_64.rpm
Retrieving http://www.percona.com/downloads/Percona-Server-5.6/LATEST/binary/redhat/6/x86_64/Percona-Server-shared-56-5.6.16-rel64.2.el6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:Percona-Server-shared-5########################################### [100%]
[root@localhost Desktop]# rpm -ivh http://www.percona.com/downloads/Percona-Server-5.6/LATEST/binary/redhat/6/x86_64/Percona-Server-client-56-5.6.16-rel64.2.el6.x86_64.rpm
Retrieving http://www.percona.com/downloads/Percona-Server-5.6/LATEST/binary/redhat/6/x86_64/Percona-Server-client-56-5.6.16-rel64.2.el6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:Percona-Server-client-5########################################### [100%]
[root@localhost Desktop]# rpm -ivh http://www.percona.com/downloads/Percona-Server-5.6/LATEST/binary/redhat/6/x86_64/Percona-Server-server-56-5.6.16-rel64.2.el6.x86_64.rpm
Retrieving http://www.percona.com/downloads/Percona-Server-5.6/LATEST/binary/redhat/6/x86_64/Percona-Server-server-56-5.6.16-rel64.2.el6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:Percona-Server-server-5########################################### [100%]
2014-04-30 00:39:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-04-30 00:39:07 19100 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-04-30 00:39:07 19100 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-30 00:39:07 19100 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-04-30 00:39:07 19100 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-30 00:39:07 19100 [Note] InnoDB: Using Linux native AIO
2014-04-30 00:39:07 19100 [Note] InnoDB: Using CPU crc32 instructions
2014-04-30 00:39:07 19100 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-04-30 00:39:07 19100 [Note] InnoDB: Completed initialization of buffer pool
2014-04-30 00:39:07 19100 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
2014-04-30 00:39:07 19100 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2014-04-30 00:39:07 19100 [Note] InnoDB: Database physically writes the file full: wait...
2014-04-30 00:39:07 19100 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
2014-04-30 00:39:07 19100 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
2014-04-30 00:39:07 19100 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2014-04-30 00:39:07 19100 [Warning] InnoDB: New log files created, LSN=45781
2014-04-30 00:39:07 19100 [Note] InnoDB: Doublewrite buffer not found: creating new
2014-04-30 00:39:07 19100 [Note] InnoDB: Doublewrite buffer created
2014-04-30 00:39:07 19100 [Note] InnoDB: 128 rollback segment(s) are active.
2014-04-30 00:39:08 19100 [Warning] InnoDB: Creating foreign key constraint system tables.
2014-04-30 00:39:08 19100 [Note] InnoDB: Foreign key constraint system tables created
2014-04-30 00:39:08 19100 [Note] InnoDB: Creating tablespace and datafile system tables.
2014-04-30 00:39:08 19100 [Note] InnoDB: Tablespace and datafile system tables created.
2014-04-30 00:39:08 19100 [Note] InnoDB: Waiting for purge to start
2014-04-30 00:39:08 19100 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.16-64.2 started; log sequence number 0
2014-04-30 00:39:08 19100 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2014-04-30 00:39:08 19100 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
2014-04-30 00:39:08 19100 [Note] Binlog end
2014-04-30 00:39:08 19100 [Note] InnoDB: FTS optimize thread exiting.
2014-04-30 00:39:08 19100 [Note] InnoDB: Starting shutdown...
2014-04-30 00:39:10 19100 [Note] InnoDB: Shutdown completed; log sequence number 1625977
 
2014-04-30 00:39:10 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2014-04-30 00:39:10 19125 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-04-30 00:39:10 19125 [Note] InnoDB: The InnoDB memory heap is disabled
2014-04-30 00:39:10 19125 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-04-30 00:39:10 19125 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-04-30 00:39:10 19125 [Note] InnoDB: Using Linux native AIO
2014-04-30 00:39:10 19125 [Note] InnoDB: Using CPU crc32 instructions
2014-04-30 00:39:10 19125 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-04-30 00:39:10 19125 [Note] InnoDB: Completed initialization of buffer pool
2014-04-30 00:39:10 19125 [Note] InnoDB: Highest supported file format is Barracuda.
2014-04-30 00:39:10 19125 [Note] InnoDB: 128 rollback segment(s) are active.
2014-04-30 00:39:10 19125 [Note] InnoDB: Waiting for purge to start
2014-04-30 00:39:10 19125 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.16-64.2 started; log sequence number 1625977
2014-04-30 00:39:10 19125 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2014-04-30 00:39:10 19125 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
2014-04-30 00:39:10 19125 [Note] Binlog end
2014-04-30 00:39:10 19125 [Note] InnoDB: FTS optimize thread exiting.
2014-04-30 00:39:10 19125 [Note] InnoDB: Starting shutdown...
2014-04-30 00:39:12 19125 [Note] InnoDB: Shutdown completed; log sequence number 1625987
 
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
 
  /usr/bin/mysqladmin -u root password 'new-password'
  /usr/bin/mysqladmin -u root -h localhost.localdomain password 'new-password'
 
Alternatively you can run:
 
  /usr/bin/mysql_secure_installation
 
which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.
 
See the manual for more instructions.
 
Please report any problems at http://bugs.mysql.com/
 
The latest information about MySQL is available on the web at
 
  http://www.mysql.com
 
Support MySQL by buying support/licenses at http://shop.mysql.com
 
WARNING: Default config file /etc/my.cnf exists on the system
This file will be read by default by the MySQL server
If you do not want to use this, either remove it, or use the
--defaults-file argument to mysqld_safe when starting the server
 
Percona Server is distributed with several useful UDF (User Defined Function) from Maatkit.
Run the following commands to create these functions:
mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'"
mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'"
mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
See http://code.google.com/p/maatkit/source/browse/trunk/udf for more details

2. 配置Master,Slave的数据库参数文件

master:
# vi /etc/my.cnf
#在[mysqld]中添加
explicit_defaults_for_timestamp=true
log_bin = mysql-bin
server_id  = 1
innodb_buffer_pool_size = 128M
join_buffer_size = 128M
sort_buffer_size = 2M
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

log-bin is the binary log basename to generate binary log file names.
server-id option is used in replication to enable master and slave servers to identify themselves uniquely. On the master and each slave, you must use the server-id option to establish a unique replication ID in the range from 1 to 231.
explicit_defaults_for_timestamp是5.6关于timestamp默认行为的设置，请参考：http://www.williamsang.com/archives/818.html
sqlmode – STRICT_TRANS_TABLES – 为事务引擎启用严格模式
sqlmode – NO_ENGINE_SUBSTITUTION　如果需要的存储引擎被禁用或未编译，可以防止自动替换存储引擎。

slave:

vi /etc/my.cnf
#在[mysqld]中添加
explicit_defaults_for_timestamp=true
log_bin = mysql-bin
server_id = 2
relay_log = /var/lib/mysql/mysql-relay-bin
log_slave_updates = 1
read_only         =1
innodb_buffer_pool_size = 128M
join_buffer_size = 128M
sort_buffer_size = 2M
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

Out of the settings described above, the only essential one is the server-id part, but I have enabled log-bin too and named it similar to the one on master, so that slave can be promoted to master if and when required.
relay-log specifies the location and name of the relay log
log-slave-updates makes the slave log the replicated events to its binary log
read-only prevents data changes on the slaves, because slave is really usually used for reads

3. 启动并配置数据库

分别启动master、slave数据库：

<SHELL># service mysql start
Starting MySQL (Percona Server)......[  OK  ]

检查监听端口

<SHELL># netstat -nat
# netstat -lnap | grep 3306
tcp        0      0 :::3306                     :::*                        LISTEN      20771/mysqld

设置root密码

<SHELL># /usr/bin/mysqladmin -u root password 'debugo'
<SHELL># mysql -u root

登录并检查：

# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or g.
Your MySQL connection id is 2
Server version: 5.6.16-64.2-56-log Percona Server (GPL), Release 64.2, Revision 569
......
 
mysql> show master status
    -> G
*************************** 1. row ***************************
             File: mysql-bin.000001
         Position: 262
     Binlog_Do_DB: 
 Binlog_Ignore_DB: 
Executed_Gtid_Set: 
1 row in set (0.00 sec)
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| test               |
+--------------------+
4 rows in set (0.00 sec)

下面做一个test数据库的完整备份，并复制到slave所在的节点中：

<SHELL>#  mysqldump -uroot -pdebugo  --master-data=2 test > /root/dbdump.db

Note the user of master-data option. Use this option to dump a master replication server to produce a dump file that can be used to set up another server as a slave of the master. With the master-data value set to 2, the“change master” to statement (that indicates binlog name and position) is written as a comment at the start of the dump file for information purposes. The master-data option also turns on lock-all-tables option, which acquires a global read lock across all tables which ensures that the dump is consistent.
拷贝并导入到slave中：

<SHELL># scp /root/dbdump.db OStack02:/root
dbdump.db                                                               100%  203     0.2KB/s   00:00    
<SHELL># mysql -uroot -p test < dbdump.db 
Enter password:

配置master数据库用户：

mysql> grant replication slave,replication client on *.* to rep@'192.168.46.%' identified by 'debugo';
Query OK, 0 rows affected (0.05 sec)
mysql> grant all on test.* to rep@'192.168.46.%';
Query OK, 0 rows affected (0.00 sec)
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
 
mysql> show master status G
*************************** 1. row ***************************
             File: mysql-bin.000003
         Position: 349
     Binlog_Do_DB: 
 Binlog_Ignore_DB: 
Executed_Gtid_Set: 
1 row in set (0.00 sec)

slave数据库：

[root@localhost ~]# mysql -u root
...
mysql> grant replication slave,replication client on *.* to rep@'192.168.46.%' identified by 'debugo';
Query OK, 0 rows affected (0.05 sec)
mysql> grant all on test.* to rep@'192.168.46.%';
Query OK, 0 rows affected (0.00 sec)
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
 
mysql> change master to master_host='192.168.46.132', master_user='rep',master_password='debugo',master_log_file='mysql-bin.000001',master_log_pos=0;
Query OK, 0 rows affected, 2 warnings (0.05 sec)
mysql> start slave;
Query OK, 0 rows affected (0.04 sec)

4. 测试

在master端的test数据库中，创建test.t表并插入数据。

mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |      623 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
 
mysql> use test
Database changed
 
mysql> create table t (name varchar(10));
Query OK, 0 rows affected (0.02 sec)
 
mysql> insert into t values ('debugo');
Query OK, 1 row affected (0.00 sec)
 
mysql> commit;
Query OK, 0 rows affected (0.00 sec)
 
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |      945 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

slave端，检查数据

mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |     1126 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
 
mysql> use test;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
 
Database changed
mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t              |
+----------------+
1 row in set (0.00 sec)
 
mysql> select * from t;
+--------+
| name   |
+--------+
| debugo |
+--------+
1 row in set (0.00 sec)
 
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |     1448 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

可见两边binlog的position增量是一致的，数据被成功传送过来。

转载于:https://my.oschina.net/boltwu/blog/719838

weixin_34258078
关注
percona之复制工具介绍
03-19 103
1. pt-slave-find 功能介绍： 连接master寻找和打印mysql slave复制拓扑 使用说明 shell> pt-slave-...
用Percona XtraBackup 搭建 Mysql replication slave
lwei_998的专栏
11-12 855
用Percona XtraBackup 搭建 Mysql replication  slave 优点： 1. 可以简单方便的进行热备份，不用停机。 2. 开源免费。 Percona XtraBackup is a tool for backing up your data extremely easy and without interruption. It performs “hot
percona server5.6跟5.5的差异统计
04-26 81
一、摒弃掉的： 1、SHOW [GLOBAL] TEMPORARY TABLES功能取消，只能用TEMPORARY_TABLES 和 GLOBAL_TEMPORARY_TABLES 2、innodb_thread_co...
percona mysql 主从_percona主从配置
weixin_42361026的博客
01-28 334
Percona 为MySQL数据库服务器进行了改进，在功能和性能上较 MySQL 有着很显著的提升。该版本提升了在高负载情况下的 InnoDB 的性能、为 DBA 提供一些非常有用的性能诊断工具；另外有更多的参数和命令来控制服务器行为。--来自百度百科安装Percona一.安装Percona前的准备工作1.安装Percona的yum源yuminstallhttp://www.percona.c...
mysql5.6 relay.info_MySQL5.6 crash-safe replication一个坑
weixin_35817545的博客
01-20 57
事情起因：唯品会一个DBA找到我，说他们的slave掉电，再重启服务器以后，同步复制就挂了，报1032和1062错误，首先排查了在从库上没有写操作，之后询问了他们的参数。这是他们的参数：sync_master_info = 1sync_relay_log_info = 1relay_log_info_repository = FILE参数意思是：sql线程每次执行完了一个事务，就会记录在maste...
mysql5.6 relay.info_MySQL5.6 crash-safe replication一个坑-阿里云开发者社区
weixin_30376865的博客
01-26 54
事情起因：唯品会一个DBA找到我，说他们的slave掉电，再重启服务器以后，同步复制就挂了，报1032和1062错误，首先排查了在从库上没有写操作，之后询问了他们的参数。这是他们的参数：参数意思是：sql线程每次执行完了一个事务，就会记录在master.info和relay.info文件里。即：由于在记录relay.info的时候宕机，relay.info未更新，机器重启恢复后会从之前的POS点再...
MySQL5.6 crash-safe replication一个坑
weixin_34050427的博客
11-08 51
事情起因：唯品会一个DBA找到我，说他们的slave掉电，再重启服务器以后，同步复制就挂了，报1032和1062错误，首先排查了在从库上没有写操作，之后询问了他们的参数。 这是他们的参数： 1 2 3 sync_master_info=1 sync_relay_log_info=1 relay_log_info_repositor...
mysql5.6基于percona-xtrabackup进行全量及增量备份
weixin_45112997的博客
10-13 456
mysql5.6基于percona-xtrabackup进行全量及增量备份
Percona Server 5.6 Install （基于RPM包）
02-17 122
MySQL的安装方式一般分三种：基于RPM包安装，基于二进制包安装，基于源代码安装。不同的安装方式， 所有的知识面不一样。其实基于RPM包安装方便快捷，目录结构固定。因此，对于一般使用来说已足够。 1.安装RPM包 [root@localhostPerconaServerRPM]#rpm-...
MySQL5.6主从复制(mysql数据同步配置)
09-09
MySQL5.6主从复制是一种常见的数据库高可用性和负载均衡解决方案，它允许数据从一个主服务器（Master）实时同步到一个或多个从服务器（Slave）。这种配置使得从服务器能够处理只读查询，减轻主服务器的压力，同时...
mysql双master_MySQL运维进阶-MySQL双主(master-master)+半同步(Semisync Repl
weixin_29054399的博客
01-19 366
MySQL --> MariaDB --> Percona-ServerMySQL: oracle ,commutity : 社区版 5.5 5.6 5.7 8.0MariaDB:5.5 10.xPercona:Percona-ServerInnoDB --> XtraDBXtrabackuppercona-tools:存储引擎：引擎：也称为表类型，表级别...
MySQL复制跳过错误--slave_skip_errors、sql_slave_skip_counter、slave_exec_mode
coco3600的博客
07-22 4138
MySQL主从复制中的跳过错误处理参数--slave_skip_errors、sql_slave_skip_counter、slave_exec_mode 跳过复制错误——slave_s...
percona-toolkit常用工具的使用
qq_41401214的博客
08-23 2542
percona-toolkit工具的使用 文章目录percona-toolkit工具的使用说明安装具体工具介绍工具原理与使用pt-online-schema-change功能基本原理流程图用法使用示例pt-heartbeat功能基本原理流程图用法使用示例pt-table-checksum功能基本原理工作过程流程图用法使用示例pt-kill功能基本原理流程图用法使用示例pt-duplicate-key-checker功能基本原理用法使用示例pt-deadlock-logger功能基本原理用法使用示例pt-ta
点评项目-2-完善注册登录业务
m0_75138009的博客
09-29 477
需要处理的业务：在网页发送 /user/code 路径下的 post 请求后，我们需要检验手机号后，向合法的手机号发送一个随机生成的电话号。
Spring的热部署工具和数据库密码加盐操作
2301_77053417的博客
09-28 630
加密过程：用户输入的密码+盐值 --> 字符串1，然后使用md5对字符串1加密得到字符串2，然后字符串2+盐值 --> 字符串3，这个字符串3就是存储在数据库中的密文。背景：如果我们的密码明文存储在数据库中，要是被窃取了是非常的危险的，所以我们在数据库中存储的密码不能是明文的，需要进行加密后存储，也就是数据库中存储的是密文。解密过程：取出数据库中的盐值和用户输入的密码得到字符串1，使用md5对字符串1加密得到字符串2，然后验证字符串2和数据库中的密文即可。做好以上的步骤，你项目中的热部署就已经做好了。
k8s搭建一主三从的mysql8集群---无坑
oopxiajun博客专栏
09-27 984
对于构建基于MySQL的大规模、高性能应用来讲，需要使用水平扩展(集群)的数据库架构方式。在MySQL内建的复制功能可以实现，通过为服务器配置一个或多个备库的方式来进行数据同步。同时复制功能不仅有利于构建高性能的应用，也是高可用性、可扩展性、容灾、备份以及数据仓库等工作的基础。复制的基本原理是让一台服务器的数据与其他服务器保持同步。一台主库的数据可以同步到多台备库上，备库本身也可以被配置成另外一台服务器的主库。主库和备库之间可以有多种不同的组合方式。
[EBPF] 实时捕获DM数据库是否存在SQL阻塞
飞奔的屎壳郎
09-27 957
名称版本linux版本（centos8.5）DM88.1.4.27python利用ebpf技术在不登录数据库的情况下，通过对数据库的函数添加钩子，实时的对数据库是否存在阻塞判断现有的监控逻辑都是新建数据库用户执行SQL语句来判断阻塞情况，告警的实时性取决于监控的周期频率，而使用ebpf技术能够解决这个痛点ebpf有多种实现方式，这里便于理解测试的话 使用python语言内置c语言的形式进行了说明。涉及到生产环境应该是使用go语言或者c语言去做能够有效避免源码泄露等问题。
Redis事务
最新发布
zhzjn的博客
09-30 293
Redis事务可以通过MULTI、EXEC、WATCH和DISCARD指令来实现。1. MULTI指令：表示事务的开始，之后的所有指令都会被逐一记录，但不会立即执行。2. EXEC指令：表示事务的执行，会按照记录的指令逐一执行。3. WATCH指令：可以监视一个或多个键的变化，如果在事务执行期间被其他客户端修改，事务会被回滚。4. DISCARD指令：表示事务的撤销，可以放弃之前记录的指令。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值