In one of projects I am using Airbyte OSS along with RDS MySQL source (CDC BinLog based). Over the weekend there was some issue while running syncs. We've got following error mesage:

The error FailedRecordIteratorException with the nested Kafka Connect exception in Airbyte typically occurs during CDC (Change Data Capture) syncs from relational databases like Postgres, MySQL, or Oracle RDS.

(We suspect the issue was it could be due to binlog was deleted due to AWS RDS instance auto update) Now after three days as the BinLog is outdated (or completely new) the connection is not working and after restart it is throwing following error:

Failure in source: 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.

What is the less painful approach to restore the connection without a need to perform initial full refresh again? What would be recommended approach to handle this long term (we had similar issue alrady two months ago)?

Hey Wojtek, That error does seem like Airbyte can't find the binlog. Right now, the only approach is to trigger a full refresh. Going forward, I would check a few things: • Ensure the binlog retention period is sufficient (typically 7-10 days). From what I recall, the RDS default is 0 which purges binlogs immediately. • That the sync frequency is shorter than the binlog retention period