Summary
User is experiencing a delay of 5 minutes during the WAL resume position search in a Postgres CDC sync, with no records returned by Debezium within the timeout period.
Question
Hi All,
I am syncing postgres as CDC but in my sync i can see that max time is taken at
2024-01-17 06:29:30 [INFO ] - INFO i.d.c.p.PostgresStreamingChangeEventSource(searchWalPosition):327 Searching for WAL resume position2024-01-17 06:34:28 [INFO ] - INFO i.a.i.d.i.DebeziumRecordIterator(requestClose):208 No records were returned by Debezium in the timeout seconds 300, closing the engine and iterator
can anyone tell why it is taking 5 mints for searching WAL
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.