AWS RDS实例升级停机时间 [英] AWS RDS instance upgrade down time

问题描述

关于升级RDS实例，我有几个问题.

I have a few questions in regards to upgrading the RDS instance.

1. 将实例从小升级到大时，停机时间是多少?当您更改任何实例类型(小，大，xlarge)时，停机时间是否相对相似?或者是否存在确定因素(例如数据库大小)会改变时间?
2. 谁能分享使用RDS避免实例停机而升级实例类型的技术?在RDS中甚至有可能做到这一点.不一定要非常详细，只需一些悬崖笔记/大图片的东西即可.
3. 分配更多磁盘空间时是否会有停机时间?

推荐答案

我根本不认为这是StackOverflow的当务之急，但无论如何还是有些信息:

I don't think this is an on-topic question for StackOverflow at all, but some information anyway:

1. 这很重要，取决于数据库的大小.我已经花了一个小时或更长时间.我还创建了快照，从快照中进行了还原，并且创建了多个az，大约需要两个小时.

1. It's significant and depends on the size of the database. I've had it take an hour or more some times. I've also had creating snapshots, restoring from snapshots, and multi-az creation take around two hours before.

这取决于您现在如何配置事物.如果已经启用了多可用区，则实例升级实际上将在从属服务器上进行，然后将进行故障转移，然后将更新新的从属服务器.这会导致大约1或2分钟的实际停机时间.从属服务器上的实例升级通常需要10到20分钟左右，但是此设置没有停机时间.请注意，当执行故障转移时，Amazon在内部进行DNS交换，以便您的RDS端点指向正确的机器，因此您可能必须重新启动指向数据库的Web进程，以便它们重新连接到数据库并拉入数据库.通过新的DNS查找获得新IP.

It depends on how you have things configured now. If you have Multi-AZ already enabled, then an instance upgrade will actually occur on the slave, then a failover will occur, then the new slave is updated. This results in about 1 or 2 minutes of actual downtime. The instance upgrade on the slave usually takes around 10 to 20 minutes, but there is no downtime in this setup. Note that when it does the failover, Amazon does a DNS swap internally so that your RDS endpoint points to the right machine, so you may have to restart your web processes that point to the DB so that they reconnect to the DB and pull in the new IP from a new DNS lookup.

这篇关于AWS RDS实例升级停机时间的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！