Flink RPC通信超时 In that case, you can try to increase pekko.ask.timeout. AskTimeoutException

问题：In that case, you can try to increase pekko.ask.timeout.

可能会导致，source端和sink端中间，在创建不存在的表时，事务丢失，目标表未在首次创建会导致sink端一直无法 stream load data 成功到该目标表中，持续报错

Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: Invocation of [RemoteRpcInvocation(JobMasterOperatorEventGateway.sendRequestToCoordinator(OperatorID, SerializedValue))] at recipient [pekko.tcp://flink@172.29.105.98:6123/user/rpc/jobmanager_4] timed out. This is usually caused by: 1) Pekko failed sending the message silently, due to problems like oversized payload or serialization failures. In that case, you should find detailed error information in the logs. 2) The recipient needs more time for responding, due to problems like slow machines or network jitters. In that case, you can try to increase pekko.ask.timeout.
	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
	at org.apache.flink.cdc.runtime.operators.schema.SchemaOperator.sendRequestToCoordinator(SchemaOperator.java:318)
	... 26 more

解决：增加RPC超时时间

根据错误提示，可以尝试增加Flink的RPC超时时间。在flink-conf.yaml配置文件中增加或修改以下配置项：

pekko.ask.timeout: 5min

注意这里的配置名可能随着Flink版本的不同有所变动，具体配置项请查阅Flink 1.18版本的官方文档。

另外，checkpoint 时间也可以放开3min配置项，避免网络RPC超时

execution.checkpointing.interval: 3min

参考：Flink CDC里这种报错怎么解决？_问答-阿里云开发者社区