在Shopify升级MySQL

In early September 2021, we retired our last Shopify database virtual machine (VM) that was running Percona Server 5.7.21, marking the complete cutover to 5.7.32. In this post, I’ll share how the Database Platform team performed the most recent MySQL upgrade at Shopify. I’ll talk about some of the roadblocks we encountered during rollback testing, the internal tooling that we built out to aid upgrading and scaling our fleet in general, and our guidelines for approaching upgrades going forward, which we hope will be useful for the rest of the community.

2021年9月初，我们报废了最后一台运行Percona Server 5.7.21的Shopify数据库虚拟机（VM），标志着完全切换到了5.7.32。在这篇文章中，我将分享数据库平台团队如何在Shopify进行最新的MySQL升级。我将谈论我们在回滚测试中遇到的一些障碍，我们建立的内部工具，以帮助升级和扩展我们的舰队，以及我们对未来升级的指导方针，我们希望这将对社区的其他成员有用。

Why Upgrade and Why Now?

为什么要升级，为什么是现在？

We were particularly interested in upgrading due to the replication improvements that would preserve replication parallelism in a multi-tier replication hierarchy via transaction writesets. However, in a general sense, upgrading our version of MySQL was on our minds for a while and the reasons have become more important over time as we’ve grown:

我们对升级特别感兴趣，因为复制的改进将通过事务写集在多层复制层次中保留复制的并行性。然而，从一般意义上讲，升级我们的MySQL版本在我们的脑海中已经有一段时间了，而且随着时间的推移，随着我们的成长，这些原因变得更加重要。

We’ve transferred more load to our replicas over time, and without replication improvements, high load could cause replication lag and a poor merchant and buyer experience.
随着时间的推移，我们已经将更多的负载转移到我们的副本上，如果没有复制的改进，高负载可能会导致复制滞后，商家和买家体验不佳。
Due to our increasing global footprint, to maintain efficiency, our replication topology can be up to four “hops” deep, which increases the importance of our replication performance.
由于我们的全球足迹不断增加，为了保持效率，我们的复制拓扑结构可以达到四个 "跳 "的深度，这增加了我们复制性能的重要性。
Without replication improvements, in times of high load such as Black Friday/Cyber Monday (BFCM) and flash sales, there’s a greater likelihood of replication lag that in turn heightens the risk to merchants’ data availability in the event of a writer failure.
如果没有复制的改进，在黑色星期五/疯狂星期一（BFCM）和闪电销售等高负荷时期，复制滞后的可能性更大，这反过来又增加了...