dmcluster config failure ERROR: replication slot already exists

Connector getting Inactive due to replication slot PID already exists replication slot already exists because it's one more step to run CREATE_REPLICATION_SLOT manually So I propose the attached tiny patch to just create the slot replication slot does not exist 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

replication slot FATAL: sorry, too many clients already When replication slot in the primary server if the corresponding subscriber no longer exists