详解 InnoDB Cluster 主机名问题

最新推荐文章于 2024-05-20 17:59:33 发布
最新推荐文章于 2024-05-20 17:59:33 发布
阅读量572 收藏
点赞数
文章标签： 数据库 mysql InnoDB Cluster 组复制 dba
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/wudi53433927/article/details/128060144
版权

详解 InnoDB Cluster 主机名问题

文章目录

导言

因在写 【InnoDB Cluster】修改已有集群实例名称及成员实例选项 时发现主机名这块有一些问题，在其中进行了部分测试，但为使其内容精简，故将此部分单独拿出来形成一篇文章。要了解更多信息，请读者参阅该篇文章。

测试过程

使用cluster.setInstanceOption('旧成员实例名称','label','新成员实例名称')来修改成员实例名称。

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica3:3306','label','replica2.ic')
Setting the value of 'label' to 'replica2.ic' in the instance: 'replica3:3306' ...

Successfully set the value of 'label' to 'replica2.ic' in the cluster member: 'replica3:3306'.

cluster.status()结果：

 MySQL  ic-source:33060+ ssl  JS > cluster.status()
{
    "clusterName": "myCluster", 
    "defaultReplicaSet": {
        "name": "default", 
        "primary": "ic-source:3306", 
        "ssl": "REQUIRED", 
        "status": "OK", 
        "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", 
        "topology": {
            "ic-replica1:3306": {
                "address": "ic-replica1:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "ic-source:3306": {
                "address": "ic-source:3306", 
                "memberRole": "PRIMARY", 
                "mode": "R/W", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "replica2.ic": {
                "address": "replica3:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }
        }, 
        "topologyMode": "Single-Primary"
    }, 
    "groupInformationSourceMember": "ic-source:3306"
}

cluster.options()结果：

 MySQL  ic-source:33060+ ssl  JS > cluster.options()
 ...
         "tags": {
            "global": [], 
            "ic-replica1:3306": [], 
            "ic-source:3306": [], 
            "replica2.ic": []
        },
 ...
 
            "replica2.ic": [

注意，这里有个问题，我故意拿 replica3:3306 作为cluster.setInstanceOption()方法的实例名称参数，却依然可以运行，证明旧的实例名称并没有完全失效。那是主机缓存的问题吗？

我们来FLUSH HOSTS;试试。

mysql> flush hosts;                            
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> show warnings;
+---------+------+--------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                              |
+---------+------+--------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 1287 | 'FLUSH HOSTS' is deprecated and will be removed in a future release. Please use TRUNCATE TABLE performance_schema.host_cache instead |
+---------+------+--------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
mysql> show warnings;
+---------+------+--------------------------------------------------------------------------------------------------------------------------------------+
| Level   | Code | Message                                                                                                                              |
+---------+------+--------------------------------------------------------------------------------------------------------------------------------------+
| Warning | 1287 | 'FLUSH HOSTS' is deprecated and will be removed in a future release. Please use TRUNCATE TABLE performance_schema.host_cache instead |
+---------+------+--------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> show tables from performance_schema like 'host%';
+--------------------------------------+
| Tables_in_performance_schema (host%) |
+--------------------------------------+
| host_cache                           |
| hosts                                |
+--------------------------------------+
2 rows in set (0.04 sec)

mysql> select * from performance_schema.host_cache; 
Empty set (0.06 sec)

再次设置label选项：

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica3:3306','label','replica2')
Setting the value of 'label' to 'replica2' in the instance: 'replica3:3306' ...

Successfully set the value of 'label' to 'replica2' in the cluster member: 'replica3:3306'.
 MySQL  ic-source:33060+ ssl  JS > cluster.status()
{
    "clusterName": "myCluster", 
    "defaultReplicaSet": {
        "name": "default", 
        "primary": "ic-source:3306", 
        "ssl": "REQUIRED", 
        "status": "OK", 
        "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", 
        "topology": {
            "ic-replica1:3306": {
                "address": "ic-replica1:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "ic-source:3306": {
                "address": "ic-source:3306", 
                "memberRole": "PRIMARY", 
                "mode": "R/W", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "replica2": {
                "address": "replica3:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }
        }, 
        "topologyMode": "Single-Primary"
    }, 
    "groupInformationSourceMember": "ic-source:3306"
}

还是可以运行。那再截断performance_schema.hosts表呢？

mysql> select * from performance_schema.hosts;
+-------------+---------------------+-------------------+-------------------------------+--------------------------+
| HOST        | CURRENT_CONNECTIONS | TOTAL_CONNECTIONS | MAX_SESSION_CONTROLLED_MEMORY | MAX_SESSION_TOTAL_MEMORY |
+-------------+---------------------+-------------------+-------------------------------+--------------------------+
| NULL        |                  39 |                86 |                        272128 |                 66816672 |
| localhost   |                   2 |                 5 |                       1477504 |                  1985033 |
| ic-source   |                   0 |                45 |                       2466600 |                  2817255 |
| ic-replica1 |                   0 |                 2 |                          8240 |                    74084 |
| ic-replica2 |                   0 |                 6 |                         20576 |                   126813 |
| replica2    |                   1 |                38 |                         20576 |                    74084 |
| source      |                  15 |               159 |                       2466360 |                  2860667 |
| replica1    |                   1 |                 3 |                         20576 |                    74084 |
+-------------+---------------------+-------------------+-------------------------------+--------------------------+
8 rows in set (0.00 sec)

mysql> truncate table performance_schema.hosts;
Query OK, 0 rows affected (0.09 sec)

mysql> select * from performance_schema.hosts; 
+-----------+---------------------+-------------------+-------------------------------+--------------------------+
| HOST      | CURRENT_CONNECTIONS | TOTAL_CONNECTIONS | MAX_SESSION_CONTROLLED_MEMORY | MAX_SESSION_TOTAL_MEMORY |
+-----------+---------------------+-------------------+-------------------------------+--------------------------+
| NULL      |                  39 |                39 |                        108512 |                  1370284 |
| localhost |                   2 |                 2 |                        647040 |                   671012 |
| replica2  |                   1 |                 1 |                          8240 |                    74084 |
| source    |                  15 |                15 |                       1841072 |                  2397944 |
| replica1  |                   1 |                 1 |                          8240 |                    74084 |
+-----------+---------------------+-------------------+-------------------------------+--------------------------+
5 rows in set (0.00 sec)

再次设置label选项：

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica3:3306','label','replica2.ic')
Setting the value of 'label' to 'replica2.ic' in the instance: 'replica3:3306' ...

Successfully set the value of 'label' to 'replica2.ic' in the cluster member: 'replica3:3306'.

还是可以运行。

 MySQL  ic-source:33060+ ssl  JS > cluster.status()
 ...
            "replica2.ic": {
                "address": "replica3:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }

所以估计还是其他地方有缓存，或者和addresses可以识别出旧的实例名称。继而，我修改addresses中的mysqlClassic值为 r2-table:3306，即普通 MySQL 客户端使用的经典（标准） MySQL 协议的通讯地址。

mysql> update instances set addresses=json_replace(addresses,'$.mysqlClassic','r2-table:3306') where instance_id=4;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

mysql> select * from instances where instance_id=4;
+-------------+--------------------------------------+---------------+--------------------------------------+---------------+-------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+
| instance_id | cluster_id                           | address       | mysql_server_uuid                    | instance_name | addresses                                                                                 | attributes                                                                                                                                             | description |
+-------------+--------------------------------------+---------------+--------------------------------------+---------------+-------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+
|           4 | f465b0e3-6ce3-11ed-8310-000c298d6cb9 | replica3:3306 | 2737b324-a0f6-11ea-afd1-000c2988ff33 | replica2.ic   | {"mysqlX": "replica3:33060", "grLocal": "r2-table:3306", "mysqlClassic": "r2-table:3306"} | {"joinTime": "2022-11-26 01:12:34.768", "server_id": 1250867127, "recoveryAccountHost": "%", "recoveryAccountUser": "mysql_innodb_cluster_1250867127"} | NULL        |
+-------------+--------------------------------------+---------------+--------------------------------------+---------------+-------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+
1 row in set (0.00 sec)

然后尝试修改label，发现报错，

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica3:3306','label','replica2')
Cluster.setInstanceOption: The instance 'replica3:3306' does not belong to the cluster. (RuntimeError)

 MySQL  ic-source:33060+ ssl  JS > cluster.status()
{
    "clusterName": "myCluster", 
    "defaultReplicaSet": {
        "name": "default", 
        "primary": "ic-source:3306", 
        "ssl": "REQUIRED", 
        "status": "OK", 
        "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", 
        "topology": {
            "ic-replica1:3306": {
                "address": "ic-replica1:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "ic-source:3306": {
                "address": "ic-source:3306", 
                "memberRole": "PRIMARY", 
                "mode": "R/W", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "replica2.ic": {
                "address": "r2-table:3306", 
                "instanceErrors": [
                    "ERROR: Metadata for this instance does not match hostname reported by instance (metadata=r2-table:3306, actual=replica3:3306). Use rescan() to update the metadata."
                ], 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }
        }, 
        "topologyMode": "Single-Primary"
    }, 
    "groupInformationSourceMember": "ic-source:3306"
}

这里我们暂时先不rescan()，尝试使用其他成员实例名称（当前成员实例名称 replica2.ic，当前成员实例的 group_replication_local_address 变量值 r2-cnf:3306，和当前元数据表中新设的值 r2-table:3306 ）：

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica2.ic','label','replica2')
Cluster.setInstanceOption: The instance 'replica2.ic:3306' does not belong to the cluster. (RuntimeError)
 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('r2-cnf:3306','label','replica2')
Cluster.setInstanceOption: The instance 'r2-cnf:3306' does not belong to the cluster. (RuntimeError)
 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('r2-table:3306','label','replica2')
Cluster.setInstanceOption: The instance 'r2-table:3306' does not belong to the cluster. (RuntimeError)

再试下mysqlX的值 replica3:33060 ，显然协议都不对：

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica3:33060','label','replica2')
ERROR: Unable to connect to the target instance 'replica3:33060'. Please verify the connection settings, make sure the instance is available and try again.
Cluster.setInstanceOption: Could not open connection to 'replica3:33060': The provided URI uses the X protocol, which is not supported by this command. (RuntimeError)

都报错，证明改这个东西导致 MYSQL Shell 元数据与实际情况出现了不匹配，虽然集群仍保持高可用，成员实例仍保持在线状态，但 MYSQL Shell API 已经无法对该成员实例进行修改了。我验证了此时也仍可建立新客户端会话。由此证明mysqlClassic很重要！
图1

那么我们改回正确的值 replica3:3306 ：

mysql> update instances set addresses=json_replace(addresses,'$.mysqlClassic','replica3:3306') where instance_id=4;         
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

查看集群状态显示已经恢复了。把所有/etc/hosts中该 IP 地址对应的名称全都拿来作为成员实例名称传入该方法的第一个参数中：

 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('r2-table:3306','label','replica2')
Setting the value of 'label' to 'replica2' in the instance: 'r2-table:3306' ...

Successfully set the value of 'label' to 'replica2' in the cluster member: 'r2-table:3306'.
 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica3:3306','label','replica2.ic')
Setting the value of 'label' to 'replica2.ic' in the instance: 'replica3:3306' ...

Successfully set the value of 'label' to 'replica2.ic' in the cluster member: 'replica3:3306'.
 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('r2-cnf:3306','label','replica2')
Setting the value of 'label' to 'replica2' in the instance: 'r2-cnf:3306' ...
 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('replica2.ic:3306','label','replica2.ic')
Setting the value of 'label' to 'replica2.ic' in the instance: 'replica2.ic:3306' ...

Successfully set the value of 'label' to 'replica2.ic' in the cluster member: 'replica2.ic:3306'.
 MySQL  ic-source:33060+ ssl  JS > cluster.setInstanceOption('ic-replica2:3306','label','replica2')
Setting the value of 'label' to 'replica2' in the instance: 'ic-replica2:3306' ...

Successfully set the value of 'label' to 'replica2' in the cluster member: 'ic-replica2:3306'.

都可以运行，证明并不是只识别旧的实例名称，而是/etc/hosts中为该 IP 地址定义的所有名称！

那么为什么如此呢？前面我们已经分析得出结论，需要重启 MySQL 服务器（进程）才会将修改的主机名应用到数据库。所以这个实例名称 MySQL Shell API 是通过 MySQL 的主机名（SELECT @@hostname;）和协议使用的端口号拼接而成的。因为 MySQL 8.0.27 版本以后的 MySQL 8.0 组复制通信堆栈 支持 MySQL 通信协议 作为可选项，且 InnoDB Cluster 默认采用 MySQL 通信堆栈。所以此处的端口号是 MYSQL 默认的 3306 ，而非 XCOM 默认的 33061 。

mysql> SELECT @@group_replication_communication_stack;
+-----------------------------------------+
| @@group_replication_communication_stack |
+-----------------------------------------+
| MYSQL                                   |
+-----------------------------------------+
1 row in set (0.00 sec)

如果我们刚刚使用rescan()呢？再现刚刚的问题：

mysql> update instances set addresses=json_replace(addresses,'$.mysqlClassic','r2-table:3306') where instance_id=4;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

}
 MySQL  ic-source:33060+ ssl  JS > cluster.rescan()
Rescanning the cluster...

Result of the rescanning operation for the 'myCluster' cluster:
{
    "name": "myCluster", 
    "newTopologyMode": null, 
    "newlyDiscoveredInstances": [], 
    "unavailableInstances": [], 
    "updatedInstances": [
        {
            "host": "replica3:3306", 
            "id": 4, 
            "label": "replica2", 
            "member_id": "2737b324-a0f6-11ea-afd1-000c2988ff33", 
            "old_host": "ic-replica2:3306"
        }
    ]
}

The instance 'replica3:3306' is part of the cluster but its reported address has changed. Old address: ic-replica2:3306. Current address: replica3:3306.
Updating instance metadata...
The instance metadata for 'replica3:3306' was successfully updated.

 MySQL  ic-source:33060+ ssl  JS > cluster.status()
{
    "clusterName": "myCluster", 
    "defaultReplicaSet": {
        "name": "default", 
        "primary": "ic-source:3306", 
        "ssl": "REQUIRED", 
        "status": "OK", 
        "statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", 
        "topology": {
            "ic-replica1:3306": {
                "address": "ic-replica1:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "ic-source:3306": {
                "address": "ic-source:3306", 
                "memberRole": "PRIMARY", 
                "mode": "R/W", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }, 
            "replica2": {
                "address": "replica3:3306", 
                "memberRole": "SECONDARY", 
                "mode": "R/O", 
                "readReplicas": {}, 
                "replicationLag": "applier_queue_applied", 
                "role": "HA", 
                "status": "ONLINE", 
                "version": "8.0.31"
            }
        }, 
        "topologyMode": "Single-Primary"
    }, 
    "groupInformationSourceMember": "ic-source:3306"
}

再次印证了我刚刚的猜想。

结论

主机名这块，最关键的是 MySQL 的主机名（SELECT @@hostname;），而非操作系统当前的主机名。 当然，只要 MySQL 服务器（进程）一重启，就会读取操作系统当前的主机名作为 MySQL 的主机名（SELECT @@hostname;）。

独上西楼影三人
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
Mysql 高可用 InnoDB Cluster 多节点搭建过程
06-19
Mysql 高可用 InnoDB Cluster 多节点搭建过程
【InnoDB Cluster】修改已有集群实例名称及成员实例选项
影三人
11-27 827
【InnoDB Cluster】修改已有集群实例名称及成员实例选项
InnoDB Cluster详解
热门推荐
wzy0623的专栏
09-12 1万+
目录 一、InnoDB Cluster简介 1. 整体架构 2. MySQL Shell 3. MySQL Router 4. MySQL服务器集群 二、创建InnoDB Cluster 1. 检查实例配置 2. 配置实例 3. 创建集群 4. 向集群添加实例 5. 查看集群状态 6. 基于已有组复制的集群创建 7. 配置MySQL Router 8. 客户端连接测试 ...
MySQL InnoDB集群部署及管理全教程（一）
深圳市多克创新科技有限公司
06-12 892
MySQL InnoDB集群部署及管理全教程
MySQL InnoDB Cluster
fengge55的博客
11-29 249
这可能涉及制作文件副本、手动复制它们等等。MySQL Router作为整个InnoDB集群的流量入口(门神)，肩负着流量承接、负载均衡、成员管理以及故障转移的重任(就像前置Nginx服务器一样)，非常有必要使用一台高性能的独立服务器进行部署，还要配以足够的带宽(事实上，如果仅有一台集中式MySQL Router服务器的话，它将成为整个集群性能和可用性的瓶颈，而解决这个问题方法是接下来要讲的内容)。在默认的单主模式下，InnoDB 集群只有一个读写服务器实例–主服务器，多个辅助服务器实例是主服务器的副本。
Introducing InnoDB Cluster--2018
09-09
Set up and use InnoDB Cluster as an HA solution Migrate your existing servers to MySQL 8 Employ best practices for using InnoDB Cluster Configure servers for optimal automatic failover to ensure ...
MySQL InnoDB Cluster安装.docx
10-19
基于CentOS7 搭建基于InnoDB引擎的Mysql 8 集群环境
mysql innodb死锁问题详解.docx
01-15
数据库也会发生死锁的现象，数据库系统实现了各种死锁检测和死锁超时机制来解除死锁，锁监视器进行死锁检测，MySQL的InnoDB处理死锁的方式是 将持有最少行级排它锁的事务进行回滚，相对比较简单的死锁回滚办法
Introducing InnoDB Cluster: Learning the MySQL High Availability Stack
09-11
Set up, manage, and configure the new InnoDB Cluster feature in MySQL from Oracle. If you are growing your MySQL installation and want to explore making your servers highly available, this book ...
mysql事务(原理)
m0_74347016的博客
05-19 513
mysql事务原理
生产报表工具PI DataLInk 与 行列视之间的区别
2401_83701843的博客
05-17 245
行列视，全名“行列视生产数据应用系统”，行列视品牌所面对的业务范围远远超越了PIDatalink报表工具，他首先是一款本地部署的在线Excel文档管理系统，解决个人报表在线管理问题，其次，她和PIDataLInk一样，也是面向实时数据库报表需求的一套工具，其区别在于行列视品牌兼容国内外大多数实时数据库，也可以同时连接多个数据源，也就是她完全可以替代PI-DataLINk，同时也适用于其他品牌下的实时数据库系统；
MySQL存储过程添加二十万条数据日常练习
mi_mx的博客
05-17 301
【代码】MySQL日常练习。
MongoDB聚合运算符：$zip
superatom01的博客
05-15 355
摘要：`$zip`用于将输入数组的元素重新组合转换为新的数组，重组转换的的规则是使用输入数组的第一个元素重组为第一个数组，使用第二个元素重组为第二个数组，以此类推。
CentOS8+MySQL8.0.26+Skywalking9.7.0数据清理机制
xiaozhanfeng的博客
05-15 789
#### 代码中定义的额外模型列，这些模型列在聚合或查询时不需要，会加重负载。但激活后，用户可以看到名称，更容易自行查询数据。##### 1级聚合到2级聚合的刷新时间，默认500毫秒。##### TOPN记录报告周期，默认10分钟。##### 执行数据持久化周期，默认25秒。##### 数据清理定时器，默认5分钟。##### 明细记录有效期，默认3天。##### 监测数据有效期，默认7天。##### 会话时间阈值，默认70秒。##### 数据清理开关，默认开启。
国产化信息技术基础设施构建方案
雨笋情缘的专栏
05-20 204
随着信息技术国产化的趋势日益增强，为保障信息安全与自主可控，本方案旨在通过全面调研与科学评估，实现操作系统及基础软件的国产替代。本方案将聚焦于国产操作系统的调研与选择，以及数据库、中间件等基础软件的国产化替代方案，确保技术体系的高效稳定运行与持续发展。本方案旨在通过系统性的调研与评估，实现信息技术基础设施的国产化升级，提升系统的安全性与自主可控能力。未来，随着国产软硬件生态的不断成熟，将进一步优化技术栈，促进技术创新与产业升级，为企业的可持续发展奠定坚实的基础。兼容性：对常用应用软件、硬件设备的支持情况。
Service Worker的生命周期和全局对象和API
SaRAku的博客
05-14 814
当我们注册了Service Worker后，它会经历生命周期的各个阶段，同时会触发相应的事件。整个生命周期包括了：installing --> installed --> activating --> activated --> redundant。当Service Worker安装（installed）完毕后，会触发install事件；而激活（activated）后，则会触发activate事件。serviceWorker中，进程的全局对象（类似于window）叫做。
mysql 按区间统计 3 分钟维度
最新发布
weixin_43153309的博客
05-20 82
时间按三分钟切块，后进行统计。
【MySQL精通之路】AdminAPI-使用
Anakki的博客
05-19 610
本文介绍MySQL SHELL提供的MySQL AdminAPI，使您能够，使用它们创建和，并集成。
python连接 InnoDB Cluster获取 InnoDB Cluster状态信息
06-06
要获取InnoDB Cluster状态信息，可以使用MySQL Shell中的cluster.status()命令。具体的Python代码如下： ```python # 导入必要的模块 import mysqlx # 连接到InnoDB Cluster session = mysqlx.get_session({ "host": "localhost", "port": 33060, "user": "root", "password": "password" }) cluster = session.get_schema("mysql").get_collection("innodb_cluster_metadata").find_one()['cluster_name'] print("Connected to InnoDB Cluster: " + cluster) # 获取InnoDB Cluster状态信息 status = session.get_x().sql("SELECT * FROM performance_schema.replication_group_members").execute().fetch_all() print(status) # 关闭连接 session.close() ``` 在上面的代码中，首先使用mysqlx模块连接到InnoDB Cluster。然后使用get_x()方法获取MySQL Shell的X协议实例，并使用execute()方法执行SQL语句，获取InnoDB Cluster状态信息。最后关闭连接。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

独上西楼影三人

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值