主页 / dba / 问题 / 312115
Accepted
Mike
Asked: 2022-05-14 22:31:56 +0800 CST

Percona MySQL 5.7 到 8.0

  • 772

我想知道是否有人成功地将 percona 5.7 升级到 8.0 并具有完全填充的数据库。我读过的所有文章都表明这是可能的，但我在测试环境中尝试了两次，当升级发生时，它在服务启动期间停止并且从未真正给出真正的指示。

这是一个大型多数据库服务器，超过 100 个数据库，超过 150 GB。

我想搞定这个过程，因为当它上线时，服务器位于复制集群中。我已经读过从奴隶开始，这很好，但即使这样也表明我应该能够用数据升级。

当检查表可以升级时，它们都返回 OK。

mysql-5.7 percona

1 个回答

  1. Best Answer

    可以使用数据和回滚计划将 MySQL 5.7 迁移到 8.0

    如何检查与 MySQL 8 的兼容性。

    1. 安装 MySQL Shell（参考：在 Linux 上安装 MySQL Shell）

    2. 使用 MySQL Shell 升级检查器实用程序

       mysqlsh -- util check-for-server-upgrade { --user=root --host=localhost --port=3306 } --config-path=/etc/my.cnf

      这将产生类似于以下的输出：

      1) Usage of old temporal type
  No issues found

2) Usage of db objects with names conflicting with reserved keywords in 8.0
  No issues found

3) Usage of utf8mb3 charset
  No issues found

4) Table names in the mysql schema conflicting with new tables in 8.0
  No issues found

5) Partitioned tables using engines with non native partitioning
  No issues found

6) Foreign key constraint names longer than 64 characters
  No issues found

7) Usage of obsolete MAXDB sql_mode flag
  No issues found

8) Usage of obsolete sql_mode flags
  No issues found

9) ENUM/SET column definitions containing elements longer than 255 characters
  No issues found

10) Usage of partitioned tables in shared tablespaces
  No issues found

11) Circular directory references in tablespace data file paths
  No issues found

12) Usage of removed functions
  No issues found

13) Usage of removed GROUP BY ASC/DESC syntax
  No issues found

14) Removed system variables for error logging to the system log configuration
  To run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionary
  More information:
    https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13.html#mysqld-8-0-13-logging

15) Removed system variables
  To run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionary
  More information:
    https://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html#optvars-removed

16) System variables with new default values
  To run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionary
  More information:
    https://mysqlserverteam.com/new-defaults-in-mysql-8-0/

17) Schema inconsistencies resulting from file removal or corruption
  No issues found

18) Issues reported by 'check table x for upgrade' command
  No issues found

19) New default authentication plugin considerations
  Warning: The new default authentication plugin 'caching_sha2_password' offers
    more secure password hashing than previously used 'mysql_native_password'
    (and consequent improved client connection authentication). However, it also
    has compatibility implications that may affect existing MySQL installations.
    If your MySQL installation must serve pre-8.0 clients and you encounter
    compatibility issues after upgrading, the simplest way to address those
    issues is to reconfigure the server to revert to the previous default
    authentication plugin (mysql_native_password). For example, use these lines
    in the server option file:

    [mysqld]
    default_authentication_plugin=mysql_native_password

    However, the setting should be viewed as temporary, not as a long term or
    permanent solution, because it causes new accounts created with the setting
    in effect to forego the improved authentication security.
    If you are using replication please take time to understand how the
    authentication plugin changes may impact you.
  More information:
    https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-compatibility-issues
    https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-replication

Errors:   0
Warnings: 1
Notices:  0

    它提供了升级到 MySQL 8.0 所需的重大更改，然后您可以将这些更改应用到 MySQL 5.7。在升级到 8.0 之前。

    然后再次运行 MySQL Shell Upgrade Checker Utility 并查看问题是否已修复。

    保持与 5.7 版本相同的字符集和排序规则，以避免其他可能的冲突和问题。

    • 0

相关问题