-
Notifications
You must be signed in to change notification settings - Fork 111
replication_connection_configuration
xiaoboluo768 edited this page Jun 8, 2020
·
2 revisions
- 该表中记录从库用于连接到主库的配置参数,该表中存储的配置信息在执行change master语句时会被修改
- 与replication_connection_status表相比,replication_connection_configuration更改频率更低。因为它只包含从库连接到主库的配置参数,在连接正常工作期间这些配置信息保持不变的值,而replication_connection_status中包含的连接状态信息,只要IO线程状态发生变化,该表中的信息就会发生修改。
- replication_connection_configuration表的各字段含义以及与change master to语句的选项对应关系如下:
replication_connection_configuration表列名 | 含义 | 对应change master to语句的选项名 |
---|---|---|
CHANNEL_NAME | 显示复制通道名称 | FOR CHANNEL channel子句中的 channel |
HOST | 该通道下从库连接到主库的数据库实例IP | MASTER_HOST |
PORT | 该通道下从库连接主库的数据实例端口 | MASTER_PORT |
USER | 该通道下从库连接主库的数据库实例帐号密码 | MASTER_USER |
NETWORK_INTERFACE | 该通道下从库连接主库的数据库实例网卡名称 | MASTER_BIND |
AUTO_POSITION | 该通道下如果从库使用自动定位,则值为1,否则为0 | MASTER_AUTO_POSITION |
SSL_ALLOWED | 受否开启ssl连接,如果主库允许ssl连接且从库支持,则该选项为Yes ,如果主库不允许ssl连接则为No,如果主库允许ssl连接而从库不支持ssl连接,则为Ignored | MASTER_SSL |
SSL_CA_FILE,SSL_CA_PATH,SSL_CERTIFICATE,SSL_CIPHER,SSL_KEY,SSL_VERIFY_SERVER_CERTIFICATE,SSL_CRL_FILE,SSL_CRL_PATH | 主库使用ssl连接的ca证书,key以及是否校验ssl相关证书的选项 | MASTER_SSL_CA,MASTER_SSL_CAPATH,MASTER_SSL_CERT,MASTER_SSL_CRL,MASTER_SSL_CRLPATH,MASTER_SSL_KEY,MASTER_SSL_CIPHER,MASTER_SSL_VERIFY_SERVER_CERT |
CONNECTION_RETRY_INTERVAL | 该通道下从库连接主库丢失连接之后,从库重新连接主库每隔多少秒重试一次 | MASTER_CONNECT_RETRY |
CONNECTION_RETRY_COUNT | 该通道下允许从库重试连接主库的次数 | MASTER_RETRY_COUNT |
HEARTBEAT_INTERVAL | 该通道下从库连接主库的IO线程的保活心跳包间隔时间,以秒为单位 | MASTER_HEARTBEAT_PERIOD |
-
注意:对于replication_connection_configuration表,不允许执行TRUNCATE TABLE语句
-
表记录内容示例
admin@localhost : performance_schema 02:51:00> select * from replication_connection_configuration\G;
*************************** 1. row ***************************
CHANNEL_NAME:
HOST: 10.10.20.14
PORT: 3306
USER: qfsys
NETWORK_INTERFACE:
AUTO_POSITION: 1
SSL_ALLOWED: NO
SSL_CA_FILE:
SSL_CA_PATH:
SSL_CERTIFICATE:
SSL_CIPHER:
SSL_KEY:
SSL_VERIFY_SERVER_CERTIFICATE: NO
SSL_CRL_FILE:
SSL_CRL_PATH:
CONNECTION_RETRY_INTERVAL: 60
CONNECTION_RETRY_COUNT: 86400
HEARTBEAT_INTERVAL: 5.000
TLS_VERSION:
1 row in set (0.00 sec)
- 表结构定义
CREATE TABLE `replication_connection_configuration` (
`CHANNEL_NAME` char(64) NOT NULL,
`HOST` char(60) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`PORT` int(11) NOT NULL,
`USER` char(32) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`NETWORK_INTERFACE` char(60) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL,
`AUTO_POSITION` enum('1','0') NOT NULL,
`SSL_ALLOWED` enum('YES','NO','IGNORED') NOT NULL,
`SSL_CA_FILE` varchar(512) NOT NULL,
`SSL_CA_PATH` varchar(512) NOT NULL,
`SSL_CERTIFICATE` varchar(512) NOT NULL,
`SSL_CIPHER` varchar(512) NOT NULL,
`SSL_KEY` varchar(512) NOT NULL,
`SSL_VERIFY_SERVER_CERTIFICATE` enum('YES','NO') NOT NULL,
`SSL_CRL_FILE` varchar(255) NOT NULL,
`SSL_CRL_PATH` varchar(255) NOT NULL,
`CONNECTION_RETRY_INTERVAL` int(11) NOT NULL,
`CONNECTION_RETRY_COUNT` bigint(20) unsigned NOT NULL,
`HEARTBEAT_INTERVAL` double(10,3) unsigned NOT NULL COMMENT 'Number of seconds after which a heartbeat will be sent .',
`TLS_VERSION` varchar(255) NOT NULL
) ENGINE=PERFORMANCE_SCHEMA DEFAULT CHARSET=utf8
上一篇: replication_applier_status_by_worker表 | 下一篇: replication_connection_status表
- 验证、测试、整理:罗小波
- QQ:309969177
- 提示:本系列文章的主体结构遵循Oracle MySQL 官方 5.7 手册中,关于information_schema、mysql schema、performance_schema、sys schema的章节结构体系,并额外添加了一些验证、测试数据。鉴于本人精力和能力有限,难免出现一些纰漏,欢迎大家踊跃指正!