Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists io debezium debeziumexception_ creation of replication slot failed DebeziumException: Failed to read next byte from position 1640249837 This happens if the binlog contains any special character calavera crush slot TIP: If the query fails, it indicates that replication is not in place Go to the Setup tab of the connector, and click the Re-sync All Historical Data link

calavera crush slot Issue The Debezium connector fails to start, with a managed cloud installation of a PostgreSQL database The error message is:

christmas megaways slot This includes changes to table schemas as well as changes to the data in tables MySQL uses the binlog for replication and recovery The Debezium MySQL replication slot is already in use Here is the error from log: 2022 This occurs on line 141 here in the connector