We are using MySQL db as a source and SQL Server as a destination.
Replication seems to run great for hours, with a full load taking only 11 minutes, but after a few hours it will get this timed-out error and quit replicating...
stopping & resuming the task gets the replication working again... but it needs to be done manually
ideally, I would like to resolve the timed-out issue, but is there anyway to trigger an automatic restart of the task upon errors?
error:
00004680: 2018-11-12T13:04:25 [SOURCE_CAPTURE ]I: Read next binary log event timed-out. (mysql_endpoint_capture.c:932)
All servers are running in AWS, the source is in the Oregon region and the Attunity & Destination servers are in the Ohio region (67ms latency)
any help would be appreciated
Replication seems to run great for hours, with a full load taking only 11 minutes, but after a few hours it will get this timed-out error and quit replicating...
stopping & resuming the task gets the replication working again... but it needs to be done manually
ideally, I would like to resolve the timed-out issue, but is there anyway to trigger an automatic restart of the task upon errors?
error:
00004680: 2018-11-12T13:04:25 [SOURCE_CAPTURE ]I: Read next binary log event timed-out. (mysql_endpoint_capture.c:932)
All servers are running in AWS, the source is in the Oregon region and the Attunity & Destination servers are in the Ohio region (67ms latency)
any help would be appreciated