超过操作ChangeResourceRecordSets的速率 [英] Rate for operation ChangeResourceRecordSets exceeded

问题描述

我正在尝试删除Route 53控制台(Web界面)中的记录集，但出现此错误:

I am trying to delete record set in Route 53 console (web interface), but get this error:

超出了ChangeResourceRecordSets操作的速度

Rate for operation ChangeResourceRecordSets exceeded

我尝试通过API删除记录集，但出现相同的错误.我超过了哪个限制?

I tried deleting the record set via API, but I get the same error. Which limit have I exceeded?

推荐答案

看看. https://status.aws.amazon.com

目前(美国太平洋夏令时间2017年3月14日)，它会显示有关Route 53的错误消息.

At the moment (Mar 14, 2017 PDT) it displays an error message for Route 53.

太平洋夏令时间下午4:44，我们正在研究将DNS编辑缓慢传播到Route 53 DNS服务器的情况.这不会影响对现有DNS记录的查询.

4:44 PM PDT We are investigating slow propagation of DNS edits to the Route 53 DNS servers. This does not impact queries to existing DNS records.

5:11 PM PDT我们将继续调查DNS编辑到Route 53 DNS服务器的缓慢传播.这不会影响对现有DNS记录的查询.

5:11 PM PDT We continue to investigate slow propagation of DNS edits to the Route 53 DNS servers. This does not impact queries to existing DNS records.

6:34 PM PDT我们已经确定了DNS编辑缓慢传播到Route 53 DNS服务器的根本原因，并且正在努力进行恢复.这不会影响对现有DNS记录的查询.

6:34 PM PDT We have identified root cause of the slow propagation of DNS edits to the Route 53 DNS servers and are working towards recovery. This does not impact queries to existing DNS records.

PDT下午7:40，我们将继续经历缓慢的传播时间，并继续努力实现完全恢复.这不会影响对现有DNS记录的查询.

7:40 PM PDT We continue to experience slow propagation times and continue to work towards full recovery. This does not impact queries to existing DNS records.

PDT下午10:12我们将继续致力于解决传播速度缓慢的问题.当前正在限制对ChangeResourceRecordSets API的请求.对现有DNS记录的查询不受影响.

10:12 PM PDT We continue to work on resolving the slow propagation times. Requests to the ChangeResourceRecordSets API are currently being throttled. Queries to existing DNS records remain unaffected.

美国太平洋夏令时间3月14日，12:22，在不断传播变更的同时，我们将继续处理积压的积压工作.我们希望完全恢复还需要几个小时.我们还限制了ChangeResourceRecordSets API调用.对现有DNS记录的查询不受影响

Mar 14, 12:22 AM PDT While changes are propagating, we continue to work through the backlog of pending changes that have accumulated. We expect full recovery to take several more hours. We have also throttled ChangeResourceRecordSets API call. Queries to existing DNS records remain unaffected

最后一条陈述表明，他们限制了可以为新DNS记录进行的呼叫.

As the last statement suggests, they have throttled the calls that can be made for new DNS records.

3月14日，太平洋夏令时间上午1:40，记录更改正在缓慢传播，而我们正在处理积压的积压工作.我们仍然希望完全恢复还需要几个小时.我们将继续限制ChangeResourceRecordSets API调用.对现有DNS记录的查询不受影响.

Mar 14, 1:40 AM PDT Record changes are slowly propagating, while we work through the backlog of pending changes that have accumulated. We still expect full recovery to take several more hours. We are continuing to throttle ChangeResourceRecordSets API calls. Queries to existing DNS records remain unaffected.

3月14日，美国太平洋夏令时间(PDT)上午，记录更改仍在传播，而我们正在处理积压的积压工作.我们希望完全恢复还需要几个小时.我们将继续限制ChangeResourceRecordSets API调用.对现有DNS记录的查询不受影响.

Mar 14, 3:01 AM PDT Record changes are still propagating, while we work through the backlog of pending changes that have accumulated. We expect full recovery to take several more hours. We are continuing to throttle ChangeResourceRecordSets API calls. Queries to existing DNS records remain unaffected.

3月14日，太平洋夏令时间上午4:07，所有未完成的DNS记录更改已完成传播. ChangeResourceRecordSets API调用仍然受到限制.对现有DNS记录的查询不受影响.

Mar 14, 4:07 AM PDT All outstanding DNS record changes have completed propagating. ChangeResourceRecordSets API calls are still being throttled. Queries to existing DNS records remain unaffected.

3月14日，上午5:12 PDT ChangeResourceRecordSets在我们继续恢复的同时，API调用仍处于受限制状态.对现有DNS记录的查询不受影响.

Mar 14, 5:12 AM PDT ChangeResourceRecordSets API calls are still being throttled while we continue to recover. Queries to existing DNS records remain unaffected.

07:12 AM PDT随着我们朝着恢复的方向前进，我们继续限制一些ChangeResourceRecordSets API调用.对现有DNS记录的查询不受影响.

07:12 AM PDT We continue to throttle some ChangeResourceRecordSets API calls as we make progress towards recovery. Queries to existing DNS records remain unaffected.

07:53 PDT我们在努力实现完全恢复的同时，正在继续限制一些ChangeResourceRecordSets API调用.重试受限制的请求应该成功.对现有DNS记录的查询不受影响.

07:53 AM PDT We are continuing to throttle some ChangeResourceRecordSets API calls while we work towards full recovery. Retries for throttled requests should succeed. Queries to existing DNS records remain unaffected.

太平洋夏令时间上午10:30，我们将在恢复方面不断努力，以节制一些ChangeResourceRecordSets API调用.重试受限制的请求应该成功.对现有DNS记录的查询不受影响.

10:30 AM PDT We continue to throttle some ChangeResourceRecordSets API calls while we make progress towards recovery. Retries for throttled requests should be successful. Queries to existing DNS records remain unaffected.

可能需要更多时间才能恢复一切.但是，您的帐户或DNS设置应该没有问题.

It might take some more time until everything has recovered again. There should however be nothing wrong with your account or DNS setup.

自PDT 3月14日下午2:54更新. Route 53进程的所有限制已被删除，服务已恢复.这件事花了大约20个小时.

Update as of Mar 14 2:54 PM PDT. All throttling of the Route 53 processes has been removed and service has been restored. This incident took about 20 hours.

3月14日，太平洋夏令时间下午1:11，我们将继续恢复，以继续消除ChangeResourceRecordSets API的限制.在此阶段，随着DNS更新成功完成，许多客户看到了恢复.对于仍处于节流状态的那些客户，我们继续建议重试API请求或使用变更批次 http://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html 可以在单个请求中更新多个DNS记录.对现有DNS记录的查询不受影响.

Mar 14, 1:11 PM PDT We continue to remove throttling for the ChangeResourceRecordSets API as we continue towards recovery. At this stage, many customers are seeing recovery as DNS updates complete successful. For those customers that are still experiencing throttling, we continue to recommend retrying API requests or making use of change batches http://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html to update multiple DNS records in a single request. Queries to existing DNS records remain unaffected.

3月14日，太平洋夏令时间下午2:54，我们已为ChangeResourceRecordSets API取消了限制，并且正在恢复.现在，所有DNS更新操作均已成功完成.对现有DNS记录的查询不受影响.问题已解决，服务正常运行.

Mar 14, 2:54 PM PDT We have removed throttling for the ChangeResourceRecordSets API and are seeing recovery. All DNS update operations are now completing successfully. Queries to existing DNS records were not affected. The issue has been resolved and the service is operating normally.

这篇关于超过操作ChangeResourceRecordSets的速率的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！