[Fix][E2E] Wait for Postgres CDC WAL stream readiness - #11202
Merged
davidzollo merged 5 commits intoJun 30, 2026
Conversation
heye1005
reviewed
Jun 30, 2026
| * an isolated slot to avoid cross-test collisions when streaming jobs overlap. | ||
| */ | ||
| private String createSlotName() { | ||
| return "seatunnel_" + Long.toHexString(JobIdGenerator.newJobId()); |
Collaborator
There was a problem hiding this comment.
use GENERATED_SLOT_PREFIX
junjunclub
pushed a commit
to junjunclub/seatunnel
that referenced
this pull request
Jul 7, 2026
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
4 participants
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.
What does this PR do?
This fixes a shared Postgres CDC E2E instability that is unrelated to JDBC catalog compatibility changes in #11169.
Why was CI still failing?
The original shared-fix direction was only part of the picture. The current CI failure comes from the Debezium JSON Kafka test starting DML as soon as the snapshot row becomes visible, while the WAL stream is still attaching. In that window, intermediate row-level changes can be skipped, which is why CI only observed
3messages instead of the expected5.The reused Postgres test container can also retain generated replication slots between CDC jobs, so the branch keeps the slot isolation and cleanup changes as well.
How was this fixed?
slot.namefor eachPostgresCDCITjob invocationactivebefore issuing the Debezium JSON test DMLVerification
./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-postgres-e2e -nsu -Dmaven.gitcommitid.skip=true spotless:apply./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-postgres-e2e -nsu -Dmaven.gitcommitid.skip=true -DskipUT=true -DskipIT=false -Dit.test=PostgresCDCIT -DfailIfNoTests=false -Dskip.spotless=true verifyThe local Maven verification reached the real E2E startup path, compiled the updated test, and then stopped on a local external-environment blocker while Testcontainers tried to pull
debezium/postgres:11from Docker Hub:toomanyrequests: You have reached your unauthenticated pull rate limit. This blocked local container startup before the code path under test could finish, so the final behavior check still relies on GitHub CI.