flinkcdc从今天开始莫名奇妙的进入假死状态为什么？

flinkcdc从今天开始莫名奇妙的进入假死状态，日志里面就这些内容，mysql账号也有organization这个库的权限？2024-03-13 17:31:15,781 ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource [] - Encountered change event 'Event{header=EventHeaderV4{timestamp=1710322275000, eventType=TABLE_MAP, serverId=1735450135, headerLength=19, dataLength=66, nextPosition=13984535, flags=0}, data=TableMapEventData{tableId=593334, database='organization', table='staff', columnTypes=8, 15, 15, 15, 15, 15, 15, 17, 17, 3, 1, 17, 17, columnMetadata=0, 384, 384, 384, 168, 384, 48, 0, 0, 0, 0, 0, 0, columnNullability={6}, eventMetadata=null}}' at offset {transaction_id=null, ts_sec=1710322275, file=mysql-bin.004329, pos=13984387, gtids=038686c1-ca1c-11ec-bea6-98039b4739c8:2-53,04e80263-ff86-11ed-9901-08c0eb663086:1-559676317,12c54333-020f-11ed-b9fc-b8599f49a7e0:1-447119514,9a99d414-14b5-11ea-8fbc-506b4b473d04:1-930581016,9ae100a0-14b5-11ea-bfe2-98039b082314:1-225595311,ce632a95-98c5-11eb-b4d3-98039b0800fc:1-312416179, server_id=1735450135, event=1} for table organization.staff whose schema isn't known to this connector. One possible cause is an incomplete database history topic. Take a new snapshot in this case.
Use the mysqlbinlog tool to view the problematic event: mysqlbinlog --start-position=13984450 --stop-position=13984535 --verbose mysql-bin.004329
2024-03-13 17:31:15,785 ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource [] - Error during binlog processing. Last offset stored = null, binlog reader near position = mysql-bin.004329/13984450
2024-03-13 17:31:15,786 WARN com.ververica.cdc.connectors.mysql.debezium.task.context.MySqlErrorHandler [] - Schema for table organization.staff is null
2024-03-13 17:33:14,496 INFO org.apache.hadoop.hdfs.protocol.datatransfer.sasl.SaslDataTransferClient [] - SASL encryption trust check: localHostTrusted = false, remoteHostTrusted = false还有其他办法嘛，还是说是低版本bug？