Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-129

Debezium fails to start if any Extra GTIDs are present in MySQL

    XMLWordPrintable

Details

    Description

      We setup 2 DB's which are replicating separately from bunch of masters.

      So we have some thing like this

      M1     M2     M3    M4 **********************|             M1       M2       M3
             DB1***********************************|                     DB2
      

      The actual GTIDs are:

      GTID
      ----------------------------------------------------------------------------------
      DB1: 01261278-6ade-11e6-b36a-42010af00790:1-118306402,4d1a4918-44ba-11e6-bf12-42010af0040b:1-707983,716ec46f-d522-11e5-bb56-0242ac110004:1-12939581,ab33eb9e-89ad-11e6-877b-42010af0002d:1-3
      DB2:                                                  4d1a4918-44ba-11e6-bf12-42010af0040b:1-707637,716ec46f-d522-11e5-bb56-0242ac110004:1-12938714,f8f9cf64-86c9-11e6-8aab-42010af00004:1-4
      

      When we fail over DBZ to connect to DB1, DBZ failed with Error

      [2016-10-06 17:38:54,721] INFO Connector last known GTIDs are 4d1a4918-44ba-11e6-bf12-42010af0040b:1-707637,716ec46f-d522-11e5-bb56-0242ac110004:1-12938715,f8f9cf64-86c9-11e6-8aab-42010af00004:1-4, but MySQL has 01261278-6ade-11e6-b36a-42010af00790:1-118364883,4d1a4918-44ba-11e6-bf12-42010af0040b:1-709438,716ec46f-d522-11e5-bb56-0242ac110004:1-12944001,ab33eb9e-89ad-11e6-877b-42010af0002d:1-3 (io.debezium.connector.mysql.MySqlConnectorTask)
      

      It looks like when we fail over to another DB, in case of we have Extra GTID DBZ fails.

      Attachments

        Activity

          People

            rhauch Randall Hauch
            akshathpatkar Akshath Patkar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: