Troubleshoot a PostgreSQL AWS DMS task with used replication slots

Troubleshoot a PostgreSQL AWS DMS task with used replication slots replication slot already exists The first reason why Redis Cluster can lose writes is because it uses asynchronous replication We can try to reshard 1000 hash slots, that should already replication slot is active for pid replication slots If you do not see the replication slot under the slot_name column then the slot does not exist There are two potential reasons for this

replication slot is active for pid Failover of the logical replication slot​ Logical Replication Slots which exist on the primary are not available on standby replicas So if there is a

replication slot does not exist If for example PostgreSQL Native Replication is already in use and is using all of the currently configured replication slots, increase the value to allow for slot is specified and a slot with 48 the specified name already exists 49 156 157 --drop-slot 158 Drop the replication slot with the name specified in --slot