Why is there no activity in my BinLog Pipeline?

This may occur due to one or more reasons.

Probable cause 1: Some configurations have changed on the database, and some of the user privileges got updated.

Resolution: Check for the messages listed in the Activity Log section of the Pipeline. Iterate over the steps from the setup guide for the MySQL variant and problems listed in this article.

Probable cause 2: The Pipeline was paused for a duration longer than the purge period of the binary log files of the MySQL server. In each poll iteration, the Hevo application reads from the offset where it had last left. If it does not find the file from which it intends to read, it stops there. When a Pipeline is paused for a long duration, it is possible that old binary log files are purged.

Resolution: In case the relevant binary log files are no longer available, you may use alternate means to re-ingest the data.

Tip: It is a good practice to keep the files for a long enough period and archive them. Before purging any file, make sure that no slave is still reading it. Note that Hevo application also behaves as a slave to your server. The document Purge Binary Logs lists a couple of good practices with regards to safely purging binary log files.

Revision History