chore(recordings): don't DLQ on PostgreSQL errors #14438
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lookup for
fetchTeam
andgetTeamByToken
shouldn't fail in anon-retriable way. Maybe there is something where team_id or token isn't
valid 🤔 but that's a issue to solve with some schema
validation.
Instead we let the error bubble up to KafkaJS which will then not commit offsets
and rather perform an exponential backoff. This is key for e.g. migrating for a new
PG without needing to first bring down the recordings ingester.
Problem
Changes
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?