Flink CDC中使用TimeStamp方式的mysql datasource会包内存溢出，时间？

Flink CDC中使用TimeStamp方式的mysql datasource会包内存溢出，时间开始时间就是当开开始10分钟。大家遇到过没
2023-07-28 11:18:41,709 INFO io.debezium.connector.mysql.MySqlStreamingChangeEventSource [] - Keepalive thread is running
2023-07-28 11:18:43,677 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 1: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:18:48,611 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 2: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:18:53,601 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 3: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:18:58,608 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 4: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:19:03,601 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 5: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:19:08,592 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 6: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:19:13,608 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 7: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:19:18,604 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 8: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}
2023-07-28 11:19:21,100 INFO io.debezium.connector.mysql.MySqlStreamingChangeEventSource [] - Stopped reading binlog after 0 events, no new offset was recorded
2023-07-28 11:19:21,101 ERROR org.apache.flink.runtime.util.ClusterUncaughtExceptionHandler [] - WARNING: Thread 'blc-192.168.200.120:3306' produced an uncaught exception. If you want to fail on uncaught exceptions, then configure cluster.uncaught-exception-handling accordingly
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:3236) ~[?:1.8.0_311]
at com.github.shyiko.mysql.binlog.BinaryLogClient.readPacketSplitInChunks(BinaryLogClient.java:1099) ~[drs-server.jar:?]
at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:1052) ~[drs-server.jar:?]
at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:631) ~[drs-server.jar:?]
at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:932) ~[drs-server.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_311]
2023-07-28 11:19:23,598 INFO com.ververica.cdc.connectors.mysql.source.reader.MySqlSourceReader [] - Binlog offset on checkpoint 9: {ts_sec=1690509600, kind=TIMESTAMP, row=0, event=0}