luyomo / yomo-connector

1 stars 0 forks source link

GTID expired for some reason #1

Open luyomo opened 5 years ago

luyomo commented 5 years ago

{ "name": "source-sbtest", "connector": { "state": "RUNNING", "worker_id": "10.180.20.4:8083" }, "tasks": [ { "id": 0, "state": "FAILED", "worker_id": "10.180.20.4:8083", "trace": "org.apache.kafka.connect.errors.ConnectException: Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged. Error code: 1236; SQLSTATE: HY000.\n\tat io.debezium.connector.maria.AbstractReader.wrap(AbstractReader.java:230)\n\tat io.debezium.connector.maria.AbstractReader.failed(AbstractReader.java:197)\n\tat io.debezium.connector.maria.BinlogReader$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogReader.java:1095)\n\tat com.github.yomo.maria.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:910)\n\tat com.github.yomo.maria.binlog.BinaryLogClient.connect(BinaryLogClient.java:523)\n\tat com.github.yomo.maria.binlog.BinaryLogClient$7.run(BinaryLogClient.java:789)\n\tat java.base/java.lang.Thread.run(Thread.java:834)\nCaused by: com.github.yomo.maria.binlog.network.ServerException: Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged.\n\tat com.github.yomo.maria.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:869)\n\t... 3 more\n"
} ], "type": "source" }

  1. curl -X DELETE 10.180.20.4:8083/connectors/source-sbtest

  2. kafka-topics.sh --delete --topic sbtest.hist --bootstrap-server d2-bitsx-db-datasync102.dev.dc3.sbivc.co.jp:9092 --command-config /KFDATA/kafka/etc/kf-cmd.cfg
    , "database.history.kafka.topic" : "sbtest.hist"

  3. kafka-topics.sh --list --bootstrap-server d2-bitsx-db-datasync102.dev.dc3.sbivc.co.jp:9092 --command-config /KFDATA/kafka/etc/kf-cmd.cfg | grep source-sbtest source-sbtest source-sbtest.sbtest.t1 source-sbtest.sbtest.t2 source-sbtest.sbtest.t3

  4. kafka-topics.sh --delete --topic source-sbtest.sbtest.t1 --bootstrap-server d2-bitsx-db-datasync102.dev.dc3.sbivc.co.jp:9092 --command-config /KFDATA/kafka/etc/kf-cmd.cfg kafka-topics.sh --delete --topic source-sbtest.sbtest.t2 --bootstrap-server d2-bitsx-db-datasync102.dev.dc3.sbivc.co.jp:9092 --command-config /KFDATA/kafka/etc/kf-cmd.cfg kafka-topics.sh --delete --topic source-sbtest.sbtest.t3 --bootstrap-server d2-bitsx-db-datasync102.dev.dc3.sbivc.co.jp:9092 --command-config /KFDATA/kafka/etc/kf-cmd.cfg kafka-topics.sh --delete --topic source-sbtest --bootstrap-server d2-bitsx-db-datasync102.dev.dc3.sbivc.co.jp:9092 --command-config /KFDATA/kafka/etc/kf-cmd.cfg

  5. curl -X POST -i -H "Content-Type: application/json" http://d2-bitsx-db-datasync101.dev.dc3.sbivc.co.jp:8083/connectors --data-binary "@source-sbtest.json"