`airbyte-cron`: RESOURCE_EXHAUSTED namespace rate limit exceeded
Shows how to fix `airbyte-cron`: RESOURCE_EXHAUSTED namespace rate limit exceeded. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Delete the Airbyte namespace. The fix that worked across multiple environments: 1.
Steps
- Hit with RESOURCEEXHAUSTED namespace rate limit errors from airbyte-cron flooding every few seconds right after startup. The fix that worked across multiple environments: 1. Helm uninstall your Airbyte release. 2. Delete the Airbyte namespace. 3. Drop the temporal and temporalvisibility databases in your external Postgres (the stuck Temporal workflow state lives there). 4. Reinstall Airbyte fresh. The bad state is in the Temporal DBs, so reinstalling without dropping them just brings the errors back.
When to use
You are seeing this: Issue airbytehq/airbyte#30691 (closed, 28 comments): ### Topic Temporal issue ### Revelant information Airbyte version: 0.50.21 We are observing abnormal amount of rate limit errors from airbyte-cron. Use this skill when you run into "airbyte-cron: RESOURCE_EXHAUSTED namespace rate limit exceeded".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: 0.50.21. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/airbytehq/airbyte/issues/30691
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.