[ 
https://issues.apache.org/jira/browse/FLINK-35312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844837#comment-17844837
 ] 

vmaster.cc commented on FLINK-35312:
------------------------------------

> An exception occurred in the change event producer. This connector will be 
> restarted
--------
After restart, this may lead to following error?

2024-05-07 15:11:46.919 [debezium-engine] ERROR 
com.ververica.cdc.debezium.internal.Handover - Reporting error:
java.lang.IllegalStateException: Retrieve schema history failed, the schema 
records for engine 040e0553-c4b1-41aa-a05b-ec14759e16b5 has been removed, this 
might because the debezium engine has been shutdown due to other errors.
        at 
com.ververica.cdc.debezium.utils.DatabaseHistoryUtil.retrieveHistory(DatabaseHistoryUtil.java:77)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
com.ververica.cdc.debezium.internal.FlinkDatabaseSchemaHistory.configure(FlinkDatabaseSchemaHistory.java:82)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.relational.HistorizedRelationalDatabaseConnectorConfig.getDatabaseHistory(HistorizedRelationalDatabaseConnectorConfig.java:105)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.relational.HistorizedRelationalDatabaseSchema.<init>(HistorizedRelationalDatabaseSchema.java:39)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.connector.sqlserver.SqlServerDatabaseSchema.<init>(SqlServerDatabaseSchema.java:34)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.connector.sqlserver.SqlServerConnectorTask.start(SqlServerConnectorTask.java:84)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:130) 
~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.connector.common.BaseSourceTask.startIfNeededAndPossible(BaseSourceTask.java:207)
 ~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.connector.common.BaseSourceTask.poll(BaseSourceTask.java:148) 
~[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at io.debezium.embedded.EmbeddedEngine.run(EmbeddedEngine.java:788) 
[flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
io.debezium.embedded.ConvertingEngineBuilder$2.run(ConvertingEngineBuilder.java:188)
 [flink-sql-connector-sqlserver-cdc.jar:2.2.0]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_382]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_382]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_382]

> Insufficient number of arguments were supplied for the procedure or function 
> cdc.fn_cdc_get_all_changes_
> --------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-35312
>                 URL: https://issues.apache.org/jira/browse/FLINK-35312
>             Project: Flink
>          Issue Type: Bug
>          Components: Flink CDC
>            Reporter: yux
>            Priority: Major
>
> h3. Flink version
> 1.17.0
> h3. Flink CDC version
> 2.4.1
> h3. Database and its version
> sql server 2014
> h3. Minimal reproduce step
> 1
> h3. What did you expect to see?
> Caused by: java.lang.RuntimeException: SplitFetcher thread 22 received 
> unexpected exception while polling the records
> at 
> org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:165)
> at 
> org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:114)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> ... 1 more
> Caused by: org.apache.kafka.connect.errors.RetriableException: An exception 
> occurred in the change event producer. This connector will be restarted.
> at 
> io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:46)
> at 
> io.debezium.connector.sqlserver.SqlServerStreamingChangeEventSource.executeIteration(SqlServerStreamingChangeEventSource.java:458)
> at 
> io.debezium.connector.sqlserver.SqlServerStreamingChangeEventSource.execute(SqlServerStreamingChangeEventSource.java:138)
> at 
> com.ververica.cdc.connectors.sqlserver.source.reader.fetch.SqlServerStreamFetchTask$LsnSplitReadTask.execute(SqlServerStreamFetchTask.java:161)
> at 
> com.ververica.cdc.connectors.sqlserver.source.reader.fetch.SqlServerScanFetchTask.execute(SqlServerScanFetchTask.java:123)
> at 
> com.ververica.cdc.connectors.base.source.reader.external.IncrementalSourceScanFetcher.lambda$submitTask$0(IncrementalSourceScanFetcher.java:95)
> ... 5 more
> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: An insufficient 
> number of arguments were supplied for the procedure or function 
> cdc.fn_cdc_get_all_changes_ ... .
> at 
> com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:265)
> at 
> com.microsoft.sqlserver.jdbc.SQLServerResultSet$FetchBuffer.nextRow(SQLServerResultSet.java:5471)
> at 
> com.microsoft.sqlserver.jdbc.SQLServerResultSet.fetchBufferNext(SQLServerResultSet.java:1794)
> at 
> com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerResultSet.java:1052)
> at 
> io.debezium.pipeline.source.spi.ChangeTableResultSet.next(ChangeTableResultSet.java:63)
> at 
> io.debezium.connector.sqlserver.SqlServerStreamingChangeEventSource.lambda$executeIteration$1(SqlServerStreamingChangeEventSource.java:269)
> at io.debezium.jdbc.JdbcConnection.prepareQuery(JdbcConnection.java:606)
> at 
> io.debezium.connector.sqlserver.SqlServerConnection.getChangesForTables(SqlServerConnection.java:329)
> at 
> io.debezium.connector.sqlserver.SqlServerStreamingChangeEventSource.executeIteration(SqlServerStreamingChangeEventSource.java:251)
> ... 9 more



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to