2017-03-14 6 views
19

Je suis en train de supprimer record dans la console Route 53 (interface web), mais obtenir cette erreur:Tarif pour ChangeResourceRecordSets opération a dépassé

Rate for operation ChangeResourceRecordSets exceeded

J'ai essayé de supprimer le record via l'API, mais je reçois le même Erreur. Quelle limite ai-je dépassé?

+0

face au même problème @Kirill Zhirnov – Shiva

+0

même ici en essayant d'ajouter. Je pense que ce pourrait être un problème temporaire – kacase

+0

Haha Je reçois le même problème. Je suppose que c'est un problème avec AWS. – ndbroadbent

Répondre

25

Jetez un oeil à. https://status.aws.amazon.com

Au moment (14 mars 2017 HAP), il affiche un message d'erreur pour la route 53.

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 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 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.

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.

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.

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

Comme dernier suggère la déclaration, ils ont étranglé les appels qui peuvent être faites pour les nouveaux enregistrements 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.

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.

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.

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 We continue to throttle some ChangeResourceRecordSets API calls as we make progress towards recovery. Queries to existing DNS records remain unaffected.

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 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.

Cela pourrait prendre un peu plus de temps jusqu'à ce que tout a de nouveau récupéré. Cependant, il ne devrait pas y avoir de problème avec votre compte ou votre configuration DNS.

Mise à jour à partir de 14 mar 14h54 PDT. Tous les étranglements des processus Route 53 ont été supprimés et le service a été rétabli. Cet incident a pris environ 20 heures.

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.

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.

+0

Cela peut être dû au fait que des milliers d'utilisateurs tentent de s'éloigner de Zerigo et passent à la Route 53. Ils arrêtent leur service DNS dans 30 jours (oui, le courrier est légitime). – Sire