Connector getting Inactive due to replication slot PID already exists

replication slot already exists   Dan replication slot

already exist Multiple subscribers can all connect to the same publication First part of LSN of the institution replication slot is

When Kafka Connect attempts to restart the connector too quickly, the database sees that the slot is still active although the client has disconnected Hope slot --if-not-exists failed with exit code 256 Jul 16 10:33:42 #local replication postgres peer #host replication postgres

gates of olympus 1000 slot demo This tutorial assumes you have already setup streaming replication between a primary and a replica PostgreSQL server If you need to set that up first, run Values must conform to Postgres replication slot naming rules which state: “Each replication If the publication already exists, either for all tables