-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Fail backfill on schedule deletion #18575
Conversation
5e8a7d2
to
3ec7050
Compare
3ec7050
to
80ad7b2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the concept, I wish the RPCError
check could be tighter. It seems like it's actually gRPC, does that mean it always has a status code we could check?
I think so:
* fix: Fail backfill on schedule deletion * fix: Check first that a schedule exists * fix: Do not retry on TemporalScheduleNotFoundError * fix: Assume schedule deleted only with NOT_FOUND status
Suspect IssuesThis pull request was deployed and Sentry observed the following issues:
Did you find this useful? React with a 👍 or 👎 |
Problem
Backfills are not cleaned up properly when deleting an export. If a backfill is still running, it should stop if it's underlying schedule (batch export) is deleted.
Changes
TemporalScheduleNotFoundError
if we cannot get the schedule while waiting on the backfill runs.👉 Stay up-to-date with PostHog coding conventions for a smoother review.
How did you test this code?
Added unit tests.