简体   繁体   English

AWS RDS MySQL 在升级过程中从 5.6 复制到 5.7

[英]AWS RDS MySQL replication from 5.6 to 5.7 during the upgrade process

Context语境

Hi all, we are about to upgrade our AWS RDS MySQL instance from MySQL 5.6 to MySQL 5.7.大家好,我们即将将我们的 AWS RDS MySQL 实例从 MySQL 5.6 升级到 MySQL 5.7。 To do so, we are planning to go through the following steps为此,我们计划通过以下步骤 go

  1. Create a read replica of the primary instance创建主实例的只读副本
  2. Upgrade the read replica version from 5.6 to 5.7将只读副本版本从 5.6 升级到 5.7
  3. Stop write operations on the primary instance停止对主实例的写入操作
  4. Wait until all the data is replicated等到所有数据都复制完
  5. Promote the read replica to be the master将只读副本提升为主副本
  6. Update our DB DNS record to point to the replica endpoint更新我们的 DB DNS 记录以指向副本端点

Question问题

According to the AWS documentation the DateTime , Time and Timestamp data type has changed between MySQL 5.6 and MySQL 5.7.根据AWS 文档DateTimeTimeTimestamp数据类型在 MySQL 5.6 和 MySQL 5.7 之间发生了变化。 That's why I wonder if the replication will still work between the primary (MySQL 5.6) and the upgraded replica (MySQL 5.7) in step "4"?这就是为什么我想知道在步骤“4”中复制是否仍然可以在主副本(MySQL 5.6)和升级副本(MySQL 5.7)之间工作?

Since the primary instance will still use the old DateTime , Time and Timestamp format, what will happen in the replica that uses the new format?由于主实例仍将使用旧的DateTimeTimeTimestamp格式,在使用新格式的副本中会发生什么?

Will the data be replicated using the old format or will it be converted to fit with the new format?数据会使用旧格式复制还是转换以适应新格式?

Thanks谢谢

Yes, replication works.是的,复制有效。 If replication will not work then it will raise an error which can be visible by running "show slave status \G" query in MySQL prompt.如果复制不起作用,那么它将引发一个错误,可以通过在 MySQL 提示符中运行“显示从属状态\G”查询来查看该错误。 We have upgraded our RDS instances by following the same steps as you mentioned and we didn't encounter any issues so far.我们按照您提到的相同步骤升级了我们的 RDS 实例,到目前为止我们没有遇到任何问题。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 将MySQL 5.6升级到5.7 - Upgrade MySQL 5.6 to 5.7 创建新的 AWS RDS 实例并导入数据,而不是将 MySQL 版本从 5.6 更新到 5.7 - Create new AWS RDS instance and import data rather than update MySQL version from 5.6 to 5.7 是否可以将AWS RDS从mysql 5.7降级到较低版本(比如5.6) - Is it possible to downgrade a AWS RDS from mysql 5.7 to lower version (say 5.6) 从MySQL 5.6升级到5.7后无法再访问数据 - Data no longer accessible after upgrade from MySQL 5.6 to 5.7 mysql(aws 强制更新)从 5.6 到 5.7 导致查询变慢 - mysql (aws forced update) from 5.6 to 5.7 causing slower queries mysqldump 从 EC2 中的 MySQL 5.7 到 AWS RDS - mysqldump from MySQL 5.7 in EC2 to AWS RDS 多源复制MySQL 5.6至5.7 GTID自动位置问题 - Multi Source Replication MySQL 5.6 to 5.7 GTID Auto Position Issues MySQL 在版本 5.6 到 5.7 升级后仅返回全文搜索的部分结果 - MySQL returning only part of results from FULL TEXT SEARCH after version 5.6 to 5.7 upgrade 使用 CloudFormation 时如何将 Aurora 无服务器 MySQL 集群从 5.6 升级到 5.7 - How to upgrade Aurora serverless MySQL cluster from 5.6 to 5.7 when using CloudFormation 在Ubuntu上从5.6升级到5.7后,“ mysql -u root”不起作用 - “mysql -u root” doesn't work after upgrade from 5.6 to 5.7 on Ubuntu
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM