记录一次阿里云flink生产故障

已于 2023-02-22 15:58:27 修改
阅读量1.3k 收藏 2
点赞数
文章标签： flink mysql java
于 2023-02-22 15:54:45 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/xiaoye1360715890/article/details/129163719
版权

2022.12.9下午三点半发现flink监控报警一直显示作业反复重启,打开管理平台发现作业在不断自动重启,找到了第一行报错日志.

 

报错日志如下

2022-12-09 15:29:28,263 ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource  [] - Error during binlog processing. Last offset stored = null, binlog reader near position = mysql-bin.001675/185277142
2022-12-09 15:29:28,264 ERROR io.debezium.pipeline.ErrorHandler                            [] - Producer failure
io.debezium.DebeziumException: null
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.wrap(MySqlStreamingChangeEventSource.java:1146) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$ReaderThreadLifecycleListener.onEventDeserializationFailure(MySqlStreamingChangeEventSource.java:1193) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:958) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:606) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:850) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at java.lang.Thread.run(Thread.java:877) [?:1.8.0_302]
Caused by: java.lang.NullPointerException
	at com.github.shyiko.mysql.binlog.event.deserialization.TableMapEventDataDeserializer.readMetadata(TableMapEventDataDeserializer.java:80) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.TableMapEventDataDeserializer.deserialize(TableMapEventDataDeserializer.java:42) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.TableMapEventDataDeserializer.deserialize(TableMapEventDataDeserializer.java:27) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.deserializeEventData(EventDeserializer.java:303) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.deserializeTableMapEventData(EventDeserializer.java:281) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.nextEvent(EventDeserializer.java:228) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$1.nextEvent(MySqlStreamingChangeEventSource.java:233) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:945) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	... 3 more
2022-12-09 15:29:28,276 ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource  [] - Error during binlog processing. Last offset stored = null, binlog reader near position = mysql-bin.001675/185277142
2022-12-09 15:29:28,276 ERROR io.debezium.pipeline.ErrorHandler                            [] - Producer failure
io.debezium.DebeziumException: Failed to deserialize data of EventHeaderV4{timestamp=1670570968000, eventType=UPDATE_ROWS, serverId=1938206218, headerLength=19, dataLength=734, nextPosition=185278024, flags=0}
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.wrap(MySqlStreamingChangeEventSource.java:1146) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$ReaderThreadLifecycleListener.onEventDeserializationFailure(MySqlStreamingChangeEventSource.java:1193) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:958) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:606) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:850) [blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at java.lang.Thread.run(Thread.java:877) [?:1.8.0_302]
Caused by: com.github.shyiko.mysql.binlog.event.deserialization.EventDataDeserializationException: Failed to deserialize data of EventHeaderV4{timestamp=1670570968000, eventType=UPDATE_ROWS, serverId=1938206218, headerLength=19, dataLength=734, nextPosition=185278024, flags=0}
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.deserializeEventData(EventDeserializer.java:309) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.nextEvent(EventDeserializer.java:232) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$1.nextEvent(MySqlStreamingChangeEventSource.java:233) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:945) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	... 3 more
Caused by: com.github.shyiko.mysql.binlog.event.deserialization.MissingTableMapEventException: No TableMapEventData has been found for table id:406820. Usually that means that you have started reading binary log 'within the logical event group' (e.g. from WRITE_ROWS and not proceeding TABLE_MAP
	at com.github.shyiko.mysql.binlog.event.deserialization.AbstractRowsEventDataDeserializer.deserializeRow(AbstractRowsEventDataDeserializer.java:109) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.UpdateRowsEventDataDeserializer.deserializeRows(UpdateRowsEventDataDeserializer.java:71) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.UpdateRowsEventDataDeserializer.deserialize(UpdateRowsEventDataDeserializer.java:58) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.UpdateRowsEventDataDeserializer.deserialize(UpdateRowsEventDataDeserializer.java:33) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.deserializeEventData(EventDeserializer.java:303) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.nextEvent(EventDeserializer.java:232) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$1.nextEvent(MySqlStreamingChangeEventSource.java:233) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:945) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	... 3 more
2022-12-09 15:29:28,665 ERROR org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager [] - Received uncaught exception.
java.lang.RuntimeException: SplitFetcher thread 768 received unexpected exception while polling the records
	at org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.runOnce(SplitFetcher.java:146) ~[flink-table_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
	at org.apache.flink.connector.base.source.reader.fetcher.SplitFetcher.run(SplitFetcher.java:101) [flink-table_2.11-1.13-vvr-4.0.14-2-SNAPSHOT.jar:1.13-vvr-4.0.14-2-SNAPSHOT]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_302]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_302]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_302]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_302]
	at java.lang.Thread.run(Thread.java:877) [?:1.8.0_302]
Caused by: org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
	at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:42) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.ververica.cdc.connectors.mysql.debezium.task.context.MySqlErrorHandler.setProducerThrowable(MySqlErrorHandler.java:72) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$ReaderThreadLifecycleListener.onEventDeserializationFailure(MySqlStreamingChangeEventSource.java:1193) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:958) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:606) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:850) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	... 1 more
Caused by: io.debezium.DebeziumException
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource.wrap(MySqlStreamingChangeEventSource.java:1146) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$ReaderThreadLifecycleListener.onEventDeserializationFailure(MySqlStreamingChangeEventSource.java:1193) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:958) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:606) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:850) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	... 1 more
Caused by: java.lang.NullPointerException
	at com.github.shyiko.mysql.binlog.event.deserialization.TableMapEventDataDeserializer.readMetadata(TableMapEventDataDeserializer.java:80) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.TableMapEventDataDeserializer.deserialize(TableMapEventDataDeserializer.java:42) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.TableMapEventDataDeserializer.deserialize(TableMapEventDataDeserializer.java:27) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.deserializeEventData(EventDeserializer.java:303) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.deserializeTableMapEventData(EventDeserializer.java:281) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.event.deserialization.EventDeserializer.nextEvent(EventDeserializer.java:228) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at io.debezium.connector.mysql.MySqlStreamingChangeEventSource$1.nextEvent(MySqlStreamingChangeEventSource.java:233) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:945) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:606) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	at com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:850) ~[blob_p-ab098b2976a0009b1eaabcfae48660640b2f63ab-efc656c3c9ffddd2404de700a0f810c2:?]
	... 1 more

TableMapEventDataDeserializer,第80行代码如下

 ColumnType枚举如下

 拉取到mysql-bin.001675/185277142,用阿里云开发提供的测试类读取,打断点进入发现columnTypes[i] & 0xFF的值为20,并不在上述枚举类中,switch(null)会导致报错.

在github上找到了相关issue,原因是mysql8.0.18多了一个类型MYSQL_TYPE_TYPED_ARRAY，这个是不可见的，然后他的ID从244变成了20,导致解析不了,检查了生产的mysql配置,发现确实是8.0.18.

https://github.com/mysql/mysql-server/commit/9082b6a820f3948fd563cc32a050f5e8775f2855

 接下来就是等待阿里云flink发布新版vvr解决问题了

不跟我会神死
关注
  • 0
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
阿里云实时计算Flink版
03-06
阿里云实时计算Flink版
flinkcdc 动态的增加新的同步表到同一个作业中
samur2的博客
04-20 1万+
本文介绍了在flinkcdc 作业中，同一个作业如何实现动态新增表的功能。设想下假如你一个 CDC pipeline 监控了 4 张表，突然有天业务需求需要再加几张表，你肯定不想另起作业 (浪费资源)，那么这个feature 可以让你在当前作业直接增加需要监控的表。新增表都是先做全量再优雅地切换到增量，遇到新增监控表时不用新起作业，极大地节约了资源
Flink报错：SplitFetcher thread 0 received unexpected exception while polling the records
最新发布
qq_39889944的博客
03-27 696
针对报错的解决方案进行汇总，并展示我的解决方案
mysql guanwnag_Error while deserializing binlog event at offset
热门推荐
weixin_39781945的博客
02-01 1万+
执行同步操作的时候提示如下错误，如何排查此类问题：2020-11-30 20:49:05,118 ERROR io.debezium.connector.mysql.BinlogReader [] - Error while deserializing binlog event at offset {ts_sec=1606736089, file=mysql...
Debezium for MySQL解析binlog报错
码农无双的博客
08-07 5684
运行在Kafka Connect 分布式worker上的debezium for mysql connector报错： {"name":"debezium-mysql-source-dev","connector":{"state":"RUNNING","worker_id":&q
Debezium报错处理系列之二十五：Client requested master to start replication from impossible position
zhengzaifeidelushang的博客
09-25 459
Debezium报错处理系列之二十五：Client requested master to start replication from impossible position
【Flink】Error during binlog processing last offset stored = null binglog reader near position
九师兄
11-07 2131
1.概述 flink 读取mysql binglog的时候报错如下 Error during binlog processing last offset stored = null binglog reader near position 对应的代码如下 引入如下 原因如下 [呲牙] mysql binlog 日志被提前删除了？感觉像是找不到需要的 binlog 日志呢 查看log如下 这里可以看 估计是过期太快，这里可以设置 读取失败 应该是这个原因 https://stackoverf
flink-mysql-cdc源表配置变动导致作业失效
Tango小黄的博客
07-08 2547
如果修改了flink-mysql-cdc配置的表名范围，导致出现一个新的表，那么无论如何都无法将该表加入到状态中
Debezium指定binlog位置初始化异常排查修复
yyoc97的专栏
05-17 3195
文章目录异常现象如何复现排查定位线索定位 异常现象 最近项目需要使用Debezium指定binlog位置读取数据，当配置FileDatabaseHistory 保存offset就会出现无法识别schema异常。 14:52:18.237 [blc-9.135.12.10:3307] ERROR io.debezium.connector.mysql.MySqlStreamingChangeEventSource - Encountered change event 'Event{header=EventHe
Flink cdc 2.1.1 bug问题
qq_31866793的博客
05-16 3509
cdc数据越界，cdc 2.1.1 bug
FlinkCDC 踩坑日志
qq_31528769的博客
10-19 4821
FlinkCDC 使用遇到的问题记录
5小时玩转阿里云实时计算Flink实时湖仓-原始业务数据脚本.zip
08-25
5小时玩转阿里云实时计算Flink实时湖仓 5小时玩转阿里云实时计算Flink实时湖仓 5小时玩转阿里云实时计算Flink实时湖仓 5小时玩转阿里云实时计算Flink实时湖仓 5小时玩转阿里云实时计算Flink实时湖仓 5小时玩转阿里云...
阿里云实时计算Flink现代化实时数据流实践共55页.pd
11-09
阿里云实时计算Flink现代化实时数据流实践共55页.pdf.zip
阿里巴巴flink介绍
12-28
阿里巴巴flink介绍
阿里超大规模Flink集群运维.pdf
07-21
阿里超大规模Flink集群运维,
mysql复制风暴_技术分享 | MySQL 复制那点事 - 参数调查笔记
weixin_32448581的博客
01-19 490
技术分享 | MySQL 复制那点事 - Seconds_behind_Master 参数调查笔记作者：戴骏贤网易游戏 技术部资深数据库系统工程师。本文来源：原创投稿*爱可生开源社区出品，原创内容未经授权不得随意使用，转载请联系小编并注明来源。文章阅读时间约 15 分钟，文中著名参考文献在文末处有参考链接。1. 问题背景部门当前的数据库架构是 双主模式，既线上由 2 台互为主从的数据库搭建而成的集...
MySQL Binlog 解析工具 -Maxwell 详解
贾红平
09-19 1455
maxwell 简介 Maxwell是一个能实时读取MySQL二进制日志binlog，并生成 JSON 格式的消息，作为生产者发送给 Kafka，Kinesis、RabbitMQ、Redis、Google Cloud Pub/Sub、文件或其它平台的应用程序。它的常见应用场景有ETL、维护缓存、收集表级别的dml指标、增量到搜索引擎、数据分区迁移、切库binlog回滚方案等。官网(http://m...
Flink Cdc EOFException 的问题
qq_32323239的博客
07-05 4500
今日公司有一个Flink Cdc的任务将mysql的binlog数据同步到kudu中，但是有一天凌晨开始间歇性的报异常，任务间歇性的重启。如下： 翻遍了github issue：Debezium Connectors Throwing EOF / Connection reset while reading bin-logs · Issue #15 · osheroff/mysql-binlog-connector-java · GitHub最后在Debezuim的FAQ上找到了对此的解决方法：http
使用 mysql binlog 监听数据库变化，优化缓存操作
菜鸟爬坑之路--小菜哥的博客站
08-02 2985
最近在项目中使用到缓存，感觉优雅的使用缓存工具比较麻烦，业界主流的缓存使用方法有先删除缓存在更新数据库，或者先更新数据库在删除缓存，只不过在业务代码中对数据操作不止一处，若想实现缓存数据的清除，必须在多处地方调用清除缓存的地方，麻烦不说，要是忘记某处数据更新未同步更新缓存数据，还会造成数据不一致的问题。 前几天在研究数据库主从同步的时候，发现 mysql 的 binlog 对数据库的数据更新会做日志记录，那么只要监听数据库的更新，是不是代表着可以在一处统一维护数据和缓存的一致性。 下面就简单...
阿里云flink.1.13 如何查询方法
07-11
要查询阿里云 Flink 1.13 的方法，可以参考以下步骤： 1. 打开阿里云官网并登录您的账号。 2. 在控制台中找到 Flink 服务，可以通过在搜索框中输入 "Flink" 或者在产品列表中查找。 3. 进入 Flink 服务的页面后，您可以找到相关的文档和资源。阅读文档是了解 Flink 的方法和功能的最佳方式。 4. 阿里云提供了详细的 Flink 文档，您可以在文档中查找特定版本（如 1.13）的方法和功能说明。通常，文档会提供示例代码和详细的步骤说明。 5. 在文档中，您可以浏览不同主题的章节，如入门指南、开发指南、API 参考等。您可以根据您的需求选择相应的章节进行查询。 此外，阿里云还提供了社区和论坛，您可以参与其中的讨论并向其他开发者寻求帮助。在社区中，您可以与其他 Flink 用户交流经验、提问问题以及获取更多资源和支持。 需要注意的是，版本号为 1.13 的 Flink 在不同的时间节点可能会有更新和变化，因此建议您查阅最新的官方文档以获取最准确和最新的信息。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值