You may be experiencing a pattern of the Binlog error like below when extracting data from MySQl Integrations in Stitch.
Fatal Error Occurred - Binlog has expired for tables
The problem always stems from how did you configured certain parameters in your AWS RDS instance due to a lack of explicit specification.
As MySQL Integrations can be configured with AWS RDS instances, for MySQL integrations that are configured in this way, it means the requirements for the Binary Log Retention Period differs from that of standalone MySQL instances and this can cause issues if the Binary Log Retention Period is incorrectly or insufficiently configured.
Resolution
The Binary Log Retention Period should be configured to a value of 168 hours or 7 days.
Running call
call mysql.rds_set_configuration('binlog retention hours', 168)
or
call mysql.rds_set_configuration('binlog retention hours', 7)
will fix the issue.
Cause
The Binary Log Retention Period is controlled by AWS RDS which functions differently and independently of a standalone MySQL instance.
If the Binary Log Retention Period is set to 0, this will cause issues.
Related Content
There is a RDS specific stored procedure that governs bing log retention beyond traditional MySQL parameters given in the case.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-stored-proc-configuring.html
Environment
