My Oracle Support Banner

Replica "Got fatal error 1236" After Losing Connection to Source While Reading > 4GB Binlog (Doc ID 2018766.1)

Last updated on APRIL 12, 2021

Applies to:

MySQL Server - Version 4.0 and later
Information in this document applies to any platform.

Symptoms

Disclaimer: Starting from v8.0, some terms have been deprecated. Older releases will only use the deprecated terminology, and new releases will only use new terminology. Please see https://dev.mysql.com/doc/mysqld-version-reference/en/ for a complete list of those changes, and in which minor versions it happened.

Here is how you can identify the scenario.  Given the error log snippet:

  • Not all replicas will break due to this every time.  Therefore it is common that some replicas may be unaffected, such as if they didn't have to reconnect.
  • Changes

    Binary logs on the source are larger than 4GB in size. This often happens after changing the binlog_format from STATEMENT to ROW.

    Another change might be some bulk import or other large transactions have started occurring on the source.

    Cause

    To view full details, sign in with your My Oracle Support account.

    Don't have a My Oracle Support account? Click to get started!


    In this Document
    Symptoms
    Changes
    Cause
    Solution
     If on MySQL 5.6+
     Other solutions
    References


    My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.