Error connecting Airbyte to AWS Aurora MySQL database

Summary

Error message indicates saved offset no longer present on the server. Suggested actions include resetting the connection, increasing binlog retention, and adjusting sync frequency. MySQL documentation mentions changing binlog_expire_logs_seconds, which is not present in Aurora MySQL.


Question

Hi all, could someone please help me figure out a problem that I’m getting while trying to connect Airbyte (0.50.35) to an AWS Aurora MySQL data base, the error that I’m getting is:

Failure reason: Saved offset no longer present on the server. Please reset the connection, and then increase binlog retention and/or increase sync frequency. See <https://docs.airbyte.com/integrations/sources/mysql/mysql-troubleshooting#under-cdc-incremental-mode-there-are-still-full-refresh-syncs> for more details.
I checked the MySQL documentation and they mention changing binlog_expire_logs_seconds but that’s not present in Aurora MySQL



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["error", "connecting", "airbyte", "aws-aurora-mysql", "binlog-retention", "sync-frequency"]