Troubleshoot a PostgreSQL AWS DMS task with used replication slots

Troubleshoot a PostgreSQL AWS DMS task with used replication slots replication slot is active for pid In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to replication slot does not exist Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write

replication slot does not exist 1 Answer 1 It sounds like you've set primary_slot_name to the same slot in all three replicas Each replica must use a different replication

replication slot is active for pid 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 edf_tc1_2c59ae112747afa1 is active with PID 101120 in database postgres Slot Restart LSN 1B982ED98 Slot Flush LSN 1B982ED98