Fix zombie snapshot flows after the process restarts; fix a rare conn leak#4603
Merged
Conversation
❌ 8 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Contributor
❌ Test FailureAnalysis: All 8 failures are the same deterministic assertion in Test_MySQL_DateTime_ClickHouse_Range (expected "1900-01-01", got "1000-06-15") that fails only on the ClickHouse 8.0/latest leg because the newest ClickHouse widened its Date32 lower bound below the test's hardcoded clamp boundary — a real, reproducible version-driven breakage, not a flake. |
masterashu
approved these changes
Jul 21, 2026
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SnapshotFlowWorkflow holds a Temporal session for the entire workflow duration. It can receive a context cancellation in two cases: legit cancel from the outside and a k8s-initiated process restart. In both cases it runs a deferred cleanup that closes PG connection (important for the legit cancel). But after the process restart it doesn't own the Temporal session anymore, so CloseSlotKeepAlive can't execute (or retry), which is fine for PG as connection was closed anyway but Temporal patitently waits till a session-holding worker is available. Add ScheduleToCloseTimeout that would reap the activity Temporal-side.
Also add the same defer cleanup pattern for cdc-only mirrors as for snapshot - very minor as it's two short activities back to back but AI flagged it so it must be done.
Closes DBI-936