| Applies To | PostgreSQL Source (all variants) Pipelines with Logical Replication mode. |
| Error Message Text(s) | - Logical replication failed due to WAL expiry. Click FIX NOW to resume the data ingestion. - Unable to read data. Replication slot is stuck at IO event WALRead. Click FIX NOW to resume the data ingestion. - The PostgreSQL replication slot used by the Pipeline has become corrupt. Click FIX NOW to resume the data ingestion. |
Potential Causes
-
Hevo is unable to read the Write-Ahead Logs (WALs). This can happen due to the following reasons:
-
The WAL files have expired. This can happen if you have a sudden spike in Events which causes the WALs to expire sooner than expected, and Hevo is unable to replicate data to the Destination.
-
The PostgreSQL replication slot used by the Pipeline is not able to complete the IO event WALRead, and is waiting for data to be read from the WAL files.
-
The PostgreSQL replication slot has become corrupt.
-
Suggested Action(s)
-
In the error displayed in the Pipelines Detailed View, click FIX NOW.
-
Do one of the following:
-
Recover the lost Events by ingesting them as historical data. To do this:
-
Enable the Run Historical Load option.
-
Select the objects you want to restart the historical load for.
-
Click OK, FIX IT.
-
-
Skip the expired Events and read the latest available WAL files. To do this:
-
Disable the Run Historical Load option.
-
Click OK, FIX IT.
-
-