Details
-
Bug
-
Resolution: Unresolved
-
Major
-
1.9.3.Final
-
None
-
False
-
None
-
False
Description
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
MySQLConnector - 1.9.3.Final
What is the captured database version and mode of depoyment?
on-premise -> k8s -> debezium server
What behaviour do you expect?
I expected it not ro turn an error on startup
What behaviour do you see?
an error on start up
Do you see the same behaviour using the latest relesead Debezium version?
Tested on 1.8.1.Final + 1.9.3.Final
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
Unexpected error while connecting to MySQL and looking at BINLOG_FORMAT mode: at io.debezium.connector.mysql.MySqlConnection.isBinlogFormatRow(MySqlConnection.java:385) at io.debezium.connector.mysql.MySqlConnectorTask.validateBinlogConfiguration(MySqlConnectorTask.java:240) at io.debezium.connector.mysql.MySqlConnectorTask.start(MySqlConnectorTask.java:85) at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:130) at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:759) at io.debezium.embedded.ConvertingEngineBuilder$2.run(ConvertingEngineBuilder.java:192) at io.debezium.server.DebeziumServer.lambda$start$1(DebeziumServer.java:150) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: java.sql.SQLException: Unknown system variable 'transaction_isolation' at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129) at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:829) at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:449) at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:242) at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:198) at io.debezium.jdbc.JdbcConnection.lambda$patternBasedFactory$1(JdbcConnection.java:243) at io.debezium.jdbc.JdbcConnection.connection(JdbcConnection.java:882) at io.debezium.jdbc.JdbcConnection.connection(JdbcConnection.java:877) at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:630) at io.debezium.jdbc.JdbcConnection.queryAndMap(JdbcConnection.java:504) at io.debezium.connector.mysql.MySqlConnection.isBinlogFormatRow(MySqlConnection.java:380) ... 9 more
How to reproduce the issue using our tutorial deployment?
Debezium -> ProxySQL -> MariaDB Cluster
10.5.12-MariaDB-log (ProxySQL)
| GRANT RELOAD, REPLICATION SLAVE, BINLOG MONITOR ON . TO ... |
| GRANT SELECT, LOCK TABLES ON ... |
