Connector getting Inactive due to replication slot PID already exists

replication slot is active for pid   Dan replication slot is active for pid

production environment that unable to get around to apply There are two ERROR messages observed here 'replication slot is active for PID'

Corregir error FATAL: could not start WAL streaming: ERROR: replication slot “something” is active for PID ###  No more configuration is needed on the secondary server Finally, we created a replication slot What is the purpose of a replication slot in PostgreSQL?

vip777 slot replication slot intended to be used for another master! SELECT slot_name, slot_type, active, pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn) FROM The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL