You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task requirement: to sync mySQL table into PostgreSQL table for every 6 hours in daily
Issue: Show connection read timeout error every time
Solutions that have applied:
Suspect the mySQL table is large in size (~805MB), so added index. After added index, first run it succeed (took about 25mins to finish the sync) but after that all failed (either no result return for hours or connection timeout error show)
Set config of idleTimeout to 0, timeout to 0 and poolSize to 15 in Client.connect(), 1 day succeed once the most. Others sync will be show no result return even run for hours (it seems stuck in the middle of process and stopped at different rows every time).
Upgrade mySQL library from 2.10.2 to 2.10.3 and repeat step 1 and 2, but same result (no result for hours / connection read timeout error)
Note: Syncing 3 tables from mySQL to Postgres but only 1 table failed. The other 2 tables size in few kbs.
Deno: v1.29.4
Nessie: v2.0.10
mySQL: v2.10.3
The text was updated successfully, but these errors were encountered:
eikmei
changed the title
No return result or connection timeout error
No return result or connection read timeout error
Jun 21, 2023
Task requirement: to sync mySQL table into PostgreSQL table for every 6 hours in daily
Issue: Show connection read timeout error every time
Solutions that have applied:
idleTimeout
to 0,timeout
to 0 andpoolSize
to 15 inClient.connect()
, 1 day succeed once the most. Others sync will be show no result return even run for hours (it seems stuck in the middle of process and stopped at different rows every time).2.10.2
to2.10.3
and repeat step 1 and 2, but same result (no result for hours / connection read timeout error)Note: Syncing 3 tables from mySQL to Postgres but only 1 table failed. The other 2 tables size in few kbs.
Deno: v1.29.4
Nessie: v2.0.10
mySQL: v2.10.3
The text was updated successfully, but these errors were encountered: