DanielLeens commented on issue #10992: URL: https://github.com/apache/seatunnel/issues/10992#issuecomment-4608235727
I checked the Postgres CDC config path, and this does not look like an `initial`-mode bug by itself. The important detail is that the connector defaults `slot.name` to `seatunnel` when it is not explicitly configured. In your config, `slot.name` is not set, and the PostgreSQL-side error is exactly: - replication slot `seatunnel` already exists So the first thing to try is setting a distinct slot name explicitly, for example: ```hocon slot.name = "seatunnel_baf_aux_ds_01" ``` Then please recheck with: ```sql select slot_name, database, plugin, active from pg_replication_slots; ``` The reason I am leaning away from a framework bug is that you also mentioned the same version works on another server. That points more toward environment / instance state than toward a deterministic code-path problem. If it still reproduces after using a unique `slot.name`, please share: 1. the full `pg_replication_slots` query result before startup 2. whether another connector on the same PostgreSQL instance is also using the default `seatunnel` slot 3. the PostgreSQL server log around the failed slot-creation attempt With that information we can determine whether there is still a connector-side issue to fix. -- 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]
