PolarDB-X 如 何 做 生 态兼 容 好的 MySQL 兼容性可以做到什么程度 胡中泉（舟济） 阿里云数据库解决方案架构师为什么要兼容 MySQL 01 The longer you look back, the farther you can look forward.也从阿里巴巴的“去IOE”运动说起 业务驱动下的分布式技术实践之路 5月17日，支付宝最后一台小型 机下线标志去IOE落下帷幕 反推出了天价账单也谈所谓的“中间件” 中间件只是起点，PolarDB-X 可能是离终点最近的那个 对近十年的探索以及五年的上云 经验进行重新思考，面向未来设 从运维视角实现计算存储一体化 计新架构 产品形态 基于MySQL XA实现分布式事务 基于外部组件进行扩容 支持扩容 分布式事务 一体化尝试 Review 2.0 开源 2016 2017 2018 2019 2020 2021 2021年10月20日，云栖大会宣 it probably is a duck.业务系统 上游 Single Source of Truth 问题背景 数据孤岛怎么办？ 下游MySQL 怎么做 Binlog Maxwell DebeziumPolarDB-X 完全兼容 MySQL Binlog 可行性 • 多节点产生多个增量事件队列 • 不同队列中事件之间的顺序 • 分布式事务完整性 • DDL 引起的多 Schema

102 EulerTest 103 pkgship 105 QuickIssue 106 Compatibility and Technical Assessment 107 OSV Technical Assessment 107 openEuler Compatibility List 108 openEuler Technical Assessment 110 Acknowledgment innovation versions. Each LTS version has a relatively stable performance, reliability, and compatibility. Innovation versions: released biannually between LTS versions, featuring the latest technical cloud native, big data CND, MEC, industrial control,etc. Integrated ecosystems and extensive compatibility through distributed kits Arm, x86, RISC-V, SW-64, LoongArch, Power, 100+ servers, and 300+

Notes 3.1 Installation See the installation_from_source section for full details. 3.2 Version compatibility Older agents from Zabbix 1.0, Zabbix 1.1.x, Zabbix 1.4.x and Zabbix 1.6.x can be used with Zabbix in the release notes of the version. Before running upgrade scripts drop the following indexes: MySQL alter table dhosts drop index dhosts_1; alter table dservices drop index dservices_1; alter table Database upgrade scripts are located in directory upgrades/dbpatches/1.8/: • MySQL: upgrades/dbpatches/1.8/mysql/patch.sql • Oracle: upgrades/dbpatches/1.8/oracle/patch.sql • PostgreSQL: upgrades/dbpatches/1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120 13 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . server will also accept historical data from 3.2 (and older) proxies, keeping partial backwards compatibility. • The default data storage period for internal, discovery and agent auto-registration events line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783 11 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . French 1.2 Daemon improvements 1.3 Miscellaneous improvements Fixed issues with mysql user parameter configuration script mysql.size parameter. It con- tained a complex bash expression and was failing if and graph sections was improved. • All frontend problems visible in Internet Explorer with ”Compatibility mode” enabled have been solved 8.1.7 New translations • American English • Chinese (Taiwan)

innovative versions. Each LTS version has a relatively stable performance, reliability, and compatibility. Innovative versions: released every half a year between LTS versions. They quickly integrate machine meets the compatibility and minimum hardware requirements. For details about hardware compatibility, see the openEuler compatibility list at https://openeuler.org/en/compatibility/. Virtual Machines Scenarios Application scenario 1: kernel CVE fixes Typical applications, such as Nginx, Redis, and MySQL, run on a physical or virtual machine. They generate many keep-alive connections and occupy a large

innovative versions. Each LTS version has a relatively stable performance, reliability, and compatibility. Innovative versions: released every half a year between LTS versions. They quickly integrate ecosystem: • Desktop environments: UKUI, DDE, and Xfce. • openEuler DevKit: Supports OS migration, compatibility evaluation, and various development tools such as secPaver, to simplify security configuration machine, check that the physical machine meets the compatibility and hardware requirements. For a full list, visit https://openeuler.org/en/compatibility/. VMs openEuler supports the following virtual

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1255 13 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . the ”data” element has been removed from all native items related to discovery, for backward compatibility Zabbix will still accept the JSON notation with a ”data” element, though its use is discouraged line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351 11 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • remove host • enable host • remove from host group • unlink from template MySQL 8.0 supported Support for MySQL 8.0 has been added. Date-based indices setup for Elasticsearch In order to properly about the oc- curred problem. Database down message from now on consists of the following content: [MySQL|PostgreSQL|Oracle|IBM DB2] database [on :] is not available:

0 码力 | 1365 页 | 16.69 MB | 1 年前

3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059 12 Version compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . will be set to 0.0001 seconds. 3 Miscellaneous improvements Fixed issues with mysql user parameter configuration script mysql.size parameter. It contained a complex bash expression and was failing if the line parameters: • printing all built-in agent items with values • testing a user parameter with ”mysql.ping” key defined in the specified configuration file • installing a ”Zabbix Agent” service for Windows