DanielLeens opened a new pull request, #11202: URL: https://github.com/apache/seatunnel/pull/11202
## What does this PR do? This fixes a shared Postgres CDC E2E instability that is unrelated to JDBC catalog compatibility changes in #11169. The root cause is that `PostgresCDCIT` reuses the default replication slot name (`seatunnel`) across multiple streaming jobs and restore flows. When CI runs overlap, one test can fail with `replication slot "seatunnel" already exists`, which then cascades into unrelated PR failures. ## How was this fixed? - assign a unique `slot.name` for each `PostgresCDCIT` job invocation - reuse the same generated slot across savepoint/restore flows in the same test - isolate the Debezium JSON Kafka consumer group with the same per-test slot identity - wire the relevant Postgres CDC E2E config files to accept `slot_name` injection ## Verification - `./mvnw spotless:apply` - `./mvnw -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-postgres-e2e -DskipUT=true -DskipIT=false -Dit.test=PostgresCDCIT -DfailIfNoTests=false -Dskip.spotless=true -o verify` The module-level E2E run reached `PostgresCDCIT`, started Docker/Testcontainers successfully after bringing Docker Desktop up, and then was blocked by the local Docker daemon network pool state: `all predefined address pools have been fully subnetted`. This is a local Docker environment limitation during validation, not a test assertion failure from the code change itself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
