External-dns: create/upsert records fail if too many AWS records to apply
restore a cluster backup will fail if you have too many records to create.
time="2018-10-06T23:44:37Z" level=error msg="InvalidChangeBatch: RDATA character limit of 32000 exceeded.\n\tstatus code: 400, request id: c855b089-c9c1-11e8-9fb5-cd7376597dff"
time="2018-10-06T23:44:37Z" level=error msg="Failed to submit all changes for the following zones: [/hostedzone/....]"
I think you need to do paged upsert/creates.
szuecs
All 18 comments
I could workaround the problem with using --aws-batch-change-size=40
Maybe the default of 4000 is not a good setting.
szuecs
on 7 Oct 2018
Yep, getting bit by this after upgrading external-dns via helm...and --aws-batch-change-size isn't available as a setting for the helm chart
ITBlogger
on 21 Dec 2018
Added it as an extraarg in values file
ITBlogger
on 21 Dec 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 27 Apr 2019
/remove-lifecycle stale
szuecs
on 27 Apr 2019
Submitted a change to stable/helm/external-dns chart to add parameter --aws-batch-change-size
sepulworld
on 29 May 2019
Anyone on external-dns team have a second to review: https://github.com/helm/charts/pull/14226 ? It would be helpful for those running into this API rate limiting issue to have this flag available in Helm chart to work with. 馃憤
sepulworld
on 3 Jun 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 1 Sep 2019
/remove-lifecycle stale
tbarrella
on 14 Sep 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 13 Dec 2019
/remove-lifecycle stale
szuecs
on 13 Dec 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 12 Mar 2020
/remove-lifecycle stale
szuecs
on 13 Mar 2020
This is hitting me too, after forcibly resetting a cluster that had a lot of ingress on it:
[Id: /hostedzone/Z35CN1VZCMW5SG]"
time="2020-05-03T00:47:21Z" level=error msg="InvalidChangeBatch: [RDATA character limit of 32000 exceeded.]\n\tstatus code: 400, request id: 9945b26e-737e-44a6-ba6e-8e6cb45100bd"
time="2020-05-03T00:47:21Z" level=error msg="Failed to submit all changes for the following zones: [/hostedzone/Z35CN1VZCMW5SG]"
postmaxin
on 3 May 2020
Starting to work on this - https://kubernetes.slack.com/archives/C771MKDKQ/p1592295222475600
OmerKahani
on 21 Jun 2020
/kind bug
seanmalloy
on 14 Aug 2020
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 12 Nov 2020
/remove-lifecycle stale
seanmalloy
on 12 Nov 2020
Related issues
deimosfr
路
3Comments
grahamhayes
路
5Comments
bzon
路
3Comments
ysoldak
路
3Comments
naveeng68
路
4Comments
Most helpful comment
Added it as an extraarg in values file