Hello, First of all I want to thank the Airbyte team to create a wonderful easy to use tool. I have been tinkering with Airbyte for a while and finally decided to implement it for my small data stack. My use case is simple and straightforward, I have a MySQL database in production which I want to replicate to a PostgreSQL instance in the local network. I had no issues (just had to make sure I read the documentation correctly) setting up Airbyte, setting source and destination. Though I'm facing a problem with the sync itself, I'm trying to sync 10 odd tables, only 2 of the tables have a lot of records in them (about 3 million in one and 300k in other), total database size should be around 2GB. I have tried 9-10 times so far but sync fails at the Normalization step for the table with maximum records. I suspect that's happening maybe because of the number of records or size of the table, Is there any work around for this or something obvious that I'm missing? Here's the log snippet of the error

normalization - 2021-11-18 23:08:42 INFO () LineGobbler(voidCall):82 - Database Error in model recipient (models/generated/airbyte_tables/cms_production/recipient.sql)
normalization - 2021-11-18 23:08:42 INFO () LineGobbler(voidCall):82 -   server closed the connection unexpectedly
normalization - 2021-11-18 23:08:42 INFO () LineGobbler(voidCall):82 -   	This probably means the server terminated abnormally
normalization - 2021-11-18 23:08:42 INFO () LineGobbler(voidCall):82 -   	before or while processing the request.

@Gaurang Swarge please share the complete logs so we can find the root cause. Hope you're enjoying Airbyte octavia loves !

Hi @[DEPRECATED] Marcos Marx Thank you for reply, here are couple of log files from 2 different attempts.

The problem is

- org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.

https://stackoverflow.com/questions/17285340/postgresql-exception-an-i-o-error-occured-while-sending-to-the-backend

So this seems like a PostgreSQL issue?

Yeah looks like this is a Postgres issue. Were you able to solve this ?

No, Not really, I Can't figure out whats causing this.

Hi @Gaurang Swarge, it looks like a connection drop. I found an interesting article that might help you give you some hints toward a resolution