Question

Why does it appear that my connector is not releasing the WAL logs?

Environment

Connector: PostgreSQL

Answer

Option 1: Drop and recreate the replication slot

1. Pause the connector.
2. Delete the replication slot in the source.
3. Allow the database to the checkpoint.
4. Create a new replication slot.
5. Click the Setup tab.
6. Click the Edit connection details link.
7. Click Re-sync All Historical Data on the setup page.
8. Unpause the connector.

Option 2: Allow the sync to continue 

1. Check to see how much disk space is available.
2. Add more space if needed.
3. Allow existing sync to continue to run.

Cause

The incremental sync is taking longer to read and update changes in the destination. This can cause the WAL logs to build up and consume a lot of disk space. This could be because of one of the following reasons:

• A lot of tables selected in the connector to sync
• A high rate of change in the database.
• WAL slot is not advancing (stuck)