Pipeline failure due to BinLog expiry

Last updated on Jun 13, 2023
Applies to MySQL Source (all variants) with BinLog Pipeline mode.
Error Message Text(s) - BinLog file has expired. Make sure you have BinLog retention of at least 72 hours in your MySQL instance.

Potential Causes

Hevo is unable to read the binary log files as they have expired. This can happen if you have a sudden spike in Events which causes the BinLog to disappear sooner than expected and Hevo is unable to replicate it.

Suggested Actions

  1. In the error that Hevo displays in the Pipelines Detailed View, click FIX NOW.

    BinLog FIX NOW

  2. Select one of the following options and perform the associated steps:

    • Restart the historical load for the selected Source objects and read the BinLog from the latest available log files. This allows you to recover all the lost Events due to the expired BinLog by ingesting events as historical data.

      1. Enable the Run Historical Load option and select the objects you want to restart the historical load for.

        Historical Load enabled

      2. Click OK, FIX IT.

    • Skip the historical load and read the BinLog from the latest available log files. Hevo skips the Events that were lost due to the expired BinLog and starts reading from the latest available log files.

      1. Disable the Run Historical Load option.

        Historical Load Disabled

      2. Click OK, FIX IT.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-05-2022 NA Brought this page under its respective Source documentation folder.
Sep-09-2021 1.71 New document.

Tell us what went wrong