Airbyte-Cron Error o.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: namespace rate limit exceeded #30472
Replies: 5 comments
-
Experienced same issue |
Beta Was this translation helpful? Give feedback.
-
Same here with version 0.50.29 on GKE on the |
Beta Was this translation helpful? Give feedback.
-
Thanks for reporting this @jrmbrgs. At the moment the I'm also experiencing this on Airbyte 0.50.33 using Docker deployment.
|
Beta Was this translation helpful? Give feedback.
-
I'm closing the discussion in favor of the issue #30691 which engineering team will work on. |
Beta Was this translation helpful? Give feedback.
-
We upgraded temporal version with @anaselmhamdi to image:
repository: temporalio/auto-setup
pullPolicy: IfNotPresent
tag: "1.22.2" |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
ENV :
Hosting : GCE w/ docker
Version : 0.50.29
Issue :
Since my upgrade from 0.50.0 to the latest 0.50.29 I see an error popping every 10 seconds from the airbyte-cron container :
Did not found any thread related to this error on Airbyte' Slack, discord or github issue...
found a thread on temporal.io https://community.temporal.io/t/resource-exhausted-namespace-rate-limit-exceeded-for-cron-job/7583
Beta Was this translation helpful? Give feedback.
All reactions