如何在 Amazon Aurora 中在标准配置和无服务器配置之间切换 [英] How do you switch between standard and serverless configurations in Amazon Aurora

问题描述

我正在查看这个亚马逊页面 - https://aws.amazon.com/rds/aurora/serverless/ 上面有这样一句话:

I am looking a this Amazon page - https://aws.amazon.com/rds/aurora/serverless/ and it has this quote:

您按秒为使用的数据库容量付费数据库处于活动状态，并且在标准和无服务器之间迁移在 AWS 管理控制台中点击几下即可配置.

You pay on a per-second basis for the database capacity you use when the database is active, and migrate between standard and serverless configurations with a few clicks in the AWS Management Console.

我有几个普通的 Aurora 集群，想将它们切换到无服务器.我看了又看，在亚马逊用户界面中找不到点击几下即可迁移"的内容.我创建了一个新的无服务器集群很好，所以我可以在短暂的中断情况下进行停止、备份和恢复 - 但如果我能在不中断的情况下做到这一点 - 那就更好了.

I have a few normal Aurora clusters and want to switch them to serverless. I have looked and looked and cannot find the "migrate with a few clicks" bit in the Amazon user interface. I made a new serverless cluster just fine and so I could do a stop, backup, and restore with a short outage - but If I can do this without an outage - that would be far superior.

那么这些几次点击"在哪里 - 或者您可能会告诉我几次点击"意味着停止、备份和恢复.无论哪种方式，我认为很多人都可以从了解很少点击"的原因中受益.

So where are these "few clicks" - or perhaps you will tell me the "few clicks" means stop, backup, and restore. Either way I think a lot of folks could benefit from knowing what "few clicks" make this happen.

推荐答案

作为对@drchuck 方法的评论 - 我们已经通过艰难的方式了解到这一点，AWS Database Migration Service 在创建 目标数据库中的架构.但是 - 有一个简单的解决方法:

As a comment on @drchuck's approach - We've learned this the hard way that AWS Database Migration Service does a bad job at creating the schema in the target database. However - there's a simple workaround:

1) 运行 mysqldump --no-data 以从源数据库中获取确切的模式.

1) Run mysqldump --no-data to get the exact schema from the source database.

2) 在目标数据库上执行转储的模式.

2) Execute the dump'd schema on the target database.

3) 在您的 DMS 任务中，在目标表准备模式下，选择截断"而不是在目标上删除表".(https://docs.aws.amazon.com/dms/最新/用户指南/CHAP_Tasks.Creating.html)

3) Within your DMS task, under target table preparation mode, choose "Truncate" instead of "Drop tables on target". (https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Tasks.Creating.html)

这样一来，DMS 就不会在目标端创建架构，而且一切运行良好(加载所有现有数据，然后近乎实时地同步正在进行的更改).

With this in place, DMS doesn't create the schema on the target side, and things work pretty well (all existing data is loaded, and then ongoing changes are sync'd in near-real-time).

我们已经多次使用这种方法来最小化停机时间.

We've used this approach for minimal downtime cutovers a few times.

这篇关于如何在 Amazon Aurora 中在标准配置和无服务器配置之间切换的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！