Error with MySQL connector

210 prikaza
Preskoči na prvu nepročitanu poruku

midhunsuk...@gmail.com

nepročitano,
12. tra 2021. 07:34:3612. 04. 2021.
u debezium
Error trace: org.apache.kafka.connect.errors.ConnectException: Could not find first log file name in binary log index file Error code: 1236; SQLSTATE: HY000.
        at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230)
        at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:196)
        at io.debezium.connector.mysql.BinlogReader$ReaderThreadLifecycleListener.onCommunicationFailure(BinlogReader.java:1129)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:958)
        at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:594)
        at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:838)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.github.shyiko.mysql.binlog.network.ServerException: Could not find first log file name in binary log index file
        at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:922)

How to prevent this one?

Joel SALMERON VIVER

nepročitano,
12. tra 2021. 07:36:0412. 04. 2021.
u debe...@googlegroups.com
Increase binlog retention, for starters…the error indicates that debezium cannot proceed to cdc as a replica, because the master has deleted the binlog file it needs from the position stored

El 12 abr 2021, a les 13:34, midhunsuk...@gmail.com <midhunsuk...@gmail.com> va escriure:

--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/4951471d-f387-4d9c-90ad-9fe92217ed12n%40googlegroups.com.

Midhun Sukumaran

nepročitano,
13. tra 2021. 13:13:3613. 04. 2021.
u debe...@googlegroups.com
But I was running it on schema_only. Why should it look for unavailable logs in that case ? 

--
Regards,
Midhun

Gunnar Morling

nepročitano,
14. tra 2021. 11:23:3414. 04. 2021.
u debezium
Also with "schema_only" snapshotting, the connector will read the actual binlog once the (schema) snapshot is complete. This mode doesn't mean "take a snapshot and stop".

--Gunnar

Midhun Sukumaran

nepročitano,
20. tra 2021. 05:41:3320. 04. 2021.
u debe...@googlegroups.com
But it should only check for the available logs in the server right? You meant to say the server is missing some in between logs? 

You received this message because you are subscribed to a topic in the Google Groups "debezium" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/debezium/ldctrcXoSiU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to debezium+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/6b0b6c91-70b2-42d1-9505-03948909d79cn%40googlegroups.com.
--
Regards,
Midhun
Odgovori svima
Odgovori autoru
Proslijedi
0 novih poruka