을 초과 :속도 내가 국도 53 콘솔 (웹 인터페이스)에서 설정 한 레코드를 삭제하지만,이 오류를 얻기 위해 노력하고
Rate for operation ChangeResourceRecordSets exceeded
내가 API를 통해 설정 한 기록을 삭제 시도를하지만 같은 얻을 오류. 어느 한도를 초과 했습니까?
을 초과 :속도 내가 국도 53 콘솔 (웹 인터페이스)에서 설정 한 레코드를 삭제하지만,이 오류를 얻기 위해 노력하고
Rate for operation ChangeResourceRecordSets exceeded
내가 API를 통해 설정 한 기록을 삭제 시도를하지만 같은 얻을 오류. 어느 한도를 초과 했습니까?
보세요. 순간
https://status.aws.amazon.com (2017년 3월 14일 태평양 서머 타임)은 마지막 문장에서 알 수 있듯이, 그들은 새 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 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
국도 53에 대한 오류 메시지를 표시 .
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.
모든 것이 다시 복구 될 때까지 시간이 더 걸릴 수 있습니다. 그러나 계정이나 DNS 설정에 아무런 문제가 없어야합니다.
3 월 14 일 오후 2시 54 분 (PDT)으로 업데이트. Route 53 프로세스의 모든 제한이 제거되고 서비스가 복원되었습니다. 이 사건은 약 20 시간이 걸렸습니다.
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.
이것은 수천 명의 사용자가 Zerigo에서 벗어나려고 시도하고 Route 53로 전환하려고 할 수 있기 때문일 수 있습니다. 이들은 30 개에서 DNS 서비스를 종료합니다 며칠 (예, 메일은 합법입니다). – Sire
같은 문제가있는 @Kirill Zhirnov – Shiva
여기에 추가하려고합니다. 나는 일시적인 문제 일 수도 있다고 생각한다. – kacase
하하 나는 똑같은 문제를 겪고있다. AWS의 문제라고 생각합니다. – ndbroadbent