Btw，能问一下为什么用 Stream API 而不是直接用 Flink SQL 么？
On Wed, 25 Nov 2020 at 00:21, Jark Wu <[email protected]> wrote: > See the docs: > https://github.com/ververica/flink-cdc-connectors/wiki/MySQL-CDC-Connector#setting-up-mysql-session-timeouts > > On Tue, 24 Nov 2020 at 23:54, yujianbo <[email protected]> wrote: > >> 一、环境: >> 1、版本：1.11.2 >> 2、flink CDC 用Stream API 从mysql 同步到kudu >> >> 二、遇到的问题现象： >> 1、目前线上已经同步了几张mysql表到kudu了，mysql的量级都在3千万左右。 >> 但是有一张mysql表同步了几次都遇到一个问题：大概能判断在全量阶段，还没到增量阶段。 >> >> >> 错误日志在下面。目前想采取“autoReconnect=true”看看来避免，到是不应该加在哪个地方，看日志感觉加了这个参数也是治标不治本，重点是为啥不发送packet，造成了卡顿？ >> >> 下面是具体报错： >> ====================================================== >> 2020-11-24 20:00:37,547 *ERROR io.debezium.connector.mysql.SnapshotReader >> * >> [] - Failed due to error: Aborting snapshot due to error when last running >> 'SELECT * FROM `uchome`.`forums_post_12`': *The last packet successfully >> received from the server was 39 milliseconds ago. The last packet sent >> successfully to the server was 6,772,615 milliseconds ago. is longer than >> the server configured value of 'wait_timeout'. You should consider either >> expiring and/or testing connection validity before use in your >> application, >> increasing the server configured values for client timeouts, or using the >> Connector/J connection property 'autoReconnect=true' to avoid this >> problem.* >> org.apache.kafka.connect.errors.ConnectException: The last packet >> successfully received from the server was 39 milliseconds ago. The last >> packet sent successfully to the server was 6,772,615 milliseconds ago. is >> longer than the server configured value of 'wait_timeout'. You should >> consider either expiring and/or testing connection validity before use in >> your application, increasing the server configured values for client >> timeouts, or using the Connector/J connection property >> 'autoReconnect=true' >> to avoid this problem. Error code: 0; SQLSTATE: 08S01. >> at >> io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230) >> >> ~[blob_p-b339a2f89b058d1dab7e01f8c235b6bcc0c26d10-90c2b905e5c1a69c13cf6a9259bd7be8:?] >> at >> io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:207) >> >> ~[blob_p-b339a2f89b058d1dab7e01f8c235b6bcc0c26d10-90c2b905e5c1a69c13cf6a9259bd7be8:?] >> at >> >> io.debezium.connector.mysql.SnapshotReader.execute(SnapshotReader.java:831) >> >> ~[blob_p-b339a2f89b058d1dab7e01f8c235b6bcc0c26d10-90c2b905e5c1a69c13cf6a9259bd7be8:?] >> at >> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >> [?:1.8.0_231] >> at >> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >> [?:1.8.0_231] >> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_231] >> *Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: The last >> packet successfully received from the server was 39 milliseconds ago. The >> last packet sent successfully to the server was 6,772,615 milliseconds >> ago. >> is longer than the server configured value of 'wait_timeout'. *You should >> consider either expiring and/or testing connection validity before use in >> your application, increasing the server configured values for client >> timeouts, or using the Connector/J connection property >> 'autoReconnect=true' >> to avoid this problem. >> at >> >> com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174) >> >> ~[blob_p-b339a2f89b058d1dab7e01f8c235b6bcc0c26d10-90c2b905e5c1a69c13cf6a9259bd7be8:?] >> at >> >> com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64) >> >> ~[blob_p-b339a2f89b058d1dab7e01f8c235b6bcc0c26d10-90c2b905e5c1a69c13cf6a9259bd7be8:?] >> =============================================== >> >> >> >> -- >> Sent from: http://apache-flink.147419.n8.nabble.com/ >> >
