flink报错：JobManager responsible for xxx lost the leadership

查看jobmanager日志：standalonesession-0-master.log

2020-05-16 21:46:53,511 WARN  akka.remote.ReliableDeliverySupervisor                        - Association with remote system [akka.tcp://flink-metrics@master:3821] has failed, address is now gated for [50] ms. Reason: [Disassociated]
2020-05-16 21:46:53,511 WARN  akka.remote.ReliableDeliverySupervisor                        - Association with remote system [akka.tcp://flink@master:6123] has failed, address is now gated for [50] ms. Reason: [Disassociated]
2020-05-16 21:47:36,620 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - The heartbeat of JobManager with id bc6c72e5dded7b29a59ecc5417a12aee timed out.
2020-05-16 21:47:36,620 INFO  org.apache.flink.runtime.taskexecutor.TaskExecutor            - Close JobManager connection for job 53a1798d17013773e5622cc42c9bb39b.
2020-05-16 21:47:36,621 INFO  org.apache.flink.runtime.taskmanager.Task                     - Attempting to fail task externally Source: Custom Source -> Map (1/2) (2dad626977317551ef95c85e3f44cc3a).
2020-05-16 21:47:36,621 INFO  org.apache.flink.runtime.taskmanager.Task                     - Source: Custom Source -> Map (1/2) (2dad626977317551ef95c85e3f44cc3a) switched from RUNNING to FAILED.
org.apache.flink.util.FlinkException: JobManager responsible for 53a1798d17013773e5622cc42c9bb39b lost the leadership.at org.apache.flink.runtime.taskexecutor.TaskExecutor.closeJobManagerConnection(TaskExecutor.java:1272)at org.apache.flink.runtime.taskexecutor.TaskExecutor.access$1200(TaskExecutor.java:154)at org.apache.flink.runtime.taskexecutor.TaskExecutor$JobManagerHeartbeatListener.notifyHeartbeatTimeout(TaskExecutor.java:1791)at org.apache.flink.runtime.heartbeat.HeartbeatMonitorImpl.run(HeartbeatMonitorImpl.java:109)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRunAsync(AkkaRpcActor.java:397)at org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:190)at org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:152)at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26)at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21)at scala.PartialFunction.applyOrElse(PartialFunction.scala:123)at scala.PartialFunction.applyOrElse$(PartialFunction.scala:122)at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21)at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:172)at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:172)at akka.actor.Actor.aroundReceive(Actor.scala:517)at akka.actor.Actor.aroundReceive$(Actor.scala:515)at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225)at akka.actor.ActorCell.receiveMessage(ActorCell.scala:592)at akka.actor.ActorCell.invoke(ActorCell.scala:561)at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258)at akka.dispatch.Mailbox.run(Mailbox.scala:225)at akka.dispatch.Mailbox.exec(Mailbox.scala:235)at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.util.concurrent.TimeoutException: The heartbeat of JobManager with id bc6c72e5dded7b29a59ecc5417a12aee timed out.at org.apache.flink.runtime.taskexecutor.TaskExecutor$JobManagerHeartbeatListener.notifyHeartbeatTimeout(TaskExecutor.java:1792)... 26 more

单从日志我没有找到问题原因（因为我太菜）。后来问同事，是因为提交了一个job，这个job中有这么一句：

System.exit(-1);

在异常的时候，执行了这句代码，导致flink所在的JVM虚拟机直接关闭了。

因此，在代码中尽量不要有这种语句。

flink报错：JobManager responsible for xxx lost the leadership相关推荐

【Flink】JobManager responsible for xx lost the leadership zk变动导致重启
文章目录 1.概述 2.原因 2.1 内存相关 1.概述 Flink程序报错 org.apache.flink.util.FlinkException: JobManager responsible ...
mitmdump 脚本使用python第三方包方法（报错：in script xxx.py: No module named ‘xxx‘）
本文仅供学习交流使用,如侵立删! mitmdump -s 调用py脚本时加载python第三方包会报错报错:in script xxx.py: No module named 'xxx' 解决方法 ...
Android Studio运行报错：无法访问XXX......请删除该文件或确保该文件位于正确的类路径子目录中
今天运行一个项目发现运行不起来了,报错错误: 无法访问XXX 错误的类文件: C:\Users\xxx\.gradle\caches\transforms-2\files-2.1\xxx\xxx(x ...
【Flink】Flink 报错 Writing records to streamload failed
1.概述 flink报错这个问题是 FLink是高频写入doris导致的
[debug] 命令行窗口运行.py文件，报错No module named XXX
问题描述: 在PyCharm中运行.py文件正常,在命令行运行.py文件报错"No module named XXX" 原因分析说到底是搜索路径的问题. PyCharm中运行的时 ...
flink报错：The types of the interface org.apache.flink.util.OutputTag could not be inferred.
测试flink报错如下: The types of the interface org.apache.flink.util.OutputTag could not be inferred. Suppo ...
Zipalign 报错 Unable to open ‘xxx.apk’ as zip archive
Zipalign 报错 Unable to open 'xxx.apk' as zip archive Zipalign 报错 Unable to open 'xxx.apk' as zip arch ...
报错Field Mapper in xxx.xxxServiceImpl required a bean of type ‘dao.xxxMapper‘ that could not be found
报错Field Mapper in xxx.xxxServiceImpl required a bean of type 'dao.xxxMapper' that could not be found ...
QT报错cannot find -lxxx(xxx为被调模型)和undefined reference to’_imp__ZN11/14xxx(xxx为自己定义)
关于解决QT报错cannot find -lxxx(xxx为被调模型)和undefined reference to'_imp__ZN11/14xxx(xxx同上)的一种方法前情提要我的项目分为计 ...

flink报错：JobManager responsible for xxx lost the leadership

flink报错：JobManager responsible for xxx lost the leadership相关推荐

最新文章

热门文章