Summary
The user is facing a ‘Socket is closed’ error when trying to unpause a sync connection between a Postgres source and destination databases after a WAL increase. They have tried increasing the initial sync timeout without success and are seeking tips to resolve the issue.
Question
Hi everyone,
We are doing sync from our production database (Postgres Source) to a our warehouse database (Postgres Destination).
Our connection was working fine before 20 august but we paused it few days to manage our billing.
The WAL increased quite a lot on our source database (status ‘extended’) without any lost because we never purge WAL.
Since the 28, we are trying to unpause the connection but it is failing with the following error : “Socket is closed”
We sometimes receive this log INFO :
2024-08-29 05:33:52 source > INFO main i.a.c.i.d.i.DebeziumRecordIterator(requestClose):276 No records were returned by Debezium in the timeout seconds 600, closing the engine and iterator
We tried to increase the initial sync timeout to the maximum (2400) but it did not help.
Do you have any pro tips to make it works ?
Thanks in advance for your help !
Note : The AI Bot tell me it can come from the fact that we do not synchronize enough table from the source.
But we are syncing 97 table over 122 from our database. Is it not enough ?
Thanks in advance for your help !
Yours faithfully,
LCDP
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.