I've found a lot of erros in discuss like: ```Hika...
# replication-troubleshooting
l
I've found a lot of erros in discuss like:
Copy code
HikariPool-2 - Connection org.postgresql.jdbc.PgConnection@6fe46b62 marked as broken because of SQLSTATE(08006), ErrorCode(0)
I've facing this issue since august but cannot find any solution. Anyone going through this and can help me out?
m
What Postgres database are you using, are you using replicas? What Airbyte connector and platform version are you using?
l
Postrges: PostgreSQL 14.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit Yes, I'm using read-replica Postgres connector: 1.0.30 Airbyte version: 0.40.14 Even setting idle-timeout to 1 minute, the sync keeps ending with warnings. We cannot increase more the timeout cause this databases have WAL replication. This was a recommendation of our database admins.
s
Hey @Leonardo de Almeida , do you see this error every time or is it transient? Can you confirm that these two parameters are set? Their default timeout is 30 seconds: •
max_standby_archive_delay
•
max_standby_streaming_delay
https://www.postgresql.org/docs/14/runtime-config-replication.html#GUC-MAX-STANDBY-ARCHIVE-DELAY In case you haven't seen this, we have some recommended settings for postgres replicas: https://docs.airbyte.com/integrations/sources/postgres/#sync-data-from-postgres-hot-standby-server And if you haven't tried it, increasing the
Initial Waiting Time in Seconds
for the connector can sometimes help with this error. Let me know once you've checked out the above info, if it doesn't help we can keep digging.
a
@Leonardo de Almeida I am wondering if the above solutions fixed this issue for you as I am experiencing the same issue
d
@Antonia As per Airbyte docs, setting hot_standby_feedback resolved the issue for me