-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
False
-
-
False
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?
debezium-connector-mysql 2.5.0.CR1
What is the connector configuration?
{
"connector.class": "io.debezium.connector.mysql.MySqlConnector",
"snapshot.locking.mode": "none",
"errors.log.include.messages": "true",
"incremental.snapshot.chunk.size": "100000",
"tasks.max": "1",
"topic.prefix": "mysql_v1.platform-assist-mysql",
"schema.history.internal.kafka.topic": "platform_assist_schema_history_v1",
"signal.data.collection": "platform_assist.debezium_signals",
"value.converter": "org.apache.kafka.connect.json.JsonConverter",
"errors.log.enable": "true",
"errors.retry.timeout": "1800000",
"database.user": "${file:/opt/cdc/secret:user}",
"database.server.id": "7580",
"time.precision.mode": "connect",
"errors.retry.delay.max.ms": "300000",
"schema.history.internal.kafka.bootstrap.servers": "xxx:9094,xxx:9094,xxx:9094",
"heartbeat.interval.ms": "60000",
"snapshot.max.threads": "20",
"database.port": "3306",
"errors.max.retries": "6",
"database.hostname": "xxx",
"database.password": "****************************************",
"name": "platform_assist-platform-assist-mysql-connector-v2",
"value.converter.schemas.enable": "false",
"table.include.list": "platform_assist.tickets",
"database.include.list": "platform_assist",
"snapshot.mode": "schema_only"
}
What is the captured database version and mode of depoyment?
aws rds mysql engine version - 8.0.41
What behaviour do you expect?
CDC should be working
What behaviour do you see?
"trace": "org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.\n\tat io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:67)\n\tat io.debezium.connector.mysql.MySqlStreamingChangeEventSource.handleEvent(MySqlStreamingChangeEventSource.java:298)\n\tat io.debezium.connector.mysql.MySqlStreamingChangeEventSource.lambda$execute$30(MySqlStreamingChangeEventSource.java:876)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.notifyEventListeners(BinaryLogClient.java:1263)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:1089)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:648)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:949)\n\tat java.base/java.lang.Thread.run(Thread.java:829)\nCaused by: io.debezium.DebeziumException: Error processing binlog event\n\t... 7 more\nCaused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'GRANT APPLICATION_PASSWORD_ADMIN, FLUSH_OPTIMIZER_COSTS, FLUSH_STATUS, FLUSH_TABLES, FLUSH_USER_RESOURCES, ROLE_ADMIN, SENSITIVE_VARIABLES_OBSERVER, SESSION_VARIABLES_ADMIN, SET_USER_ID, SHOW_ROUTINE, XA_RECOVER_ADMIN ON *.* TO 'dharmendra_singh_prod_rw'@'%' WITH GRANT OPTION'\nno viable alternative at input 'GRANT APPLICATION_PASSWORD_ADMIN, FLUSH_OPTIMIZER_COSTS, FLUSH_STATUS, FLUSH_TABLES, FLUSH_USER_RESOURCES, ROLE_ADMIN, SENSITIVE_VARIABLES_OBSERVER, SESSION_VARIABLES_ADMIN, SET_USER_ID, SHOW_ROUTINE, XA_RECOVER_ADMIN ON'\n\tat io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43)\n\tat org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41)\n\tat org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:543)\n\tat org.antlr.v4.runtime.DefaultErrorStrategy.reportNoViableAlternative(DefaultErrorStrategy.java:310)\n\tat org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:136)\n\tat io.debezium.ddl.parser.mysql.generated.MySqlParser.sqlStatements(MySqlParser.java:1272)\n\tat io.debezium.ddl.parser.mysql.generated.MySqlParser.root(MySqlParser.java:988)\n\tat io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.parseTree(MySqlAntlrDdlParser.java:74)\n\tat io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.parseTree(MySqlAntlrDdlParser.java:46)\n\tat io.debezium.antlr.AntlrDdlParser.parse(AntlrDdlParser.java:78)\n\tat io.debezium.connector.mysql.MySqlDatabaseSchema.parseDdl(MySqlDatabaseSchema.java:213)\n\tat io.debezium.connector.mysql.MySqlDatabaseSchema.parseStreamingDdl(MySqlDatabaseSchema.java:199)\n\tat io.debezium.connector.mysql.MySqlStreamingChangeEventSource.handleQueryEvent(MySqlStreamingChangeEventSource.java:508)\n\tat io.debezium.connector.mysql.MySqlStreamingChangeEventSource.lambda$execute$18(MySqlStreamingChangeEventSource.java:846)\n\tat io.debezium.connector.mysql.MySqlStreamingChangeEventSource.handleEvent(MySqlStreamingChangeEventSource.java:278)\n\t... 6 more\nCaused by: org.antlr.v4.runtime.NoViableAltException\n\tat org.antlr.v4.runtime.atn.ParserATNSimulator.noViableAlt(ParserATNSimulator.java:2028)\n\tat org.antlr.v4.runtime.atn.ParserATNSimulator.execATN(ParserATNSimulator.java:467)\n\tat org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:393)\n\tat io.debezium.ddl.parser.mysql.generated.MySqlParser.sqlStatements(MySqlParser.java:1064)\n\t... 15 more\n"
Do you see the same behaviour using the latest relesead Debezium version?
Not tested yet
Do you have the connector logs, ideally from start till finish?
Not ATM
How to reproduce the issue using our tutorial deployment?
No idea for now, will have a look
- clones
-
-
- Closed
-
