开发者社区> 问答> 正文

Flink 运行一段时间后报错

t-2cef9f5c52247f757f677c1592279fb65f096544-78ffcb691eed1982c6e6833f3b5b5872 from master/127.0.0.1:33878
2019-06-13 19:22:11,836 INFO org.apache.flink.runtime.blob.BlobClient - Downloading null/t-2cef9f5c52247f757f677c1592279fb65f096544-78ffcb691eed1982c6e6833f3b5b5872 from master/127.0.0.1:33878
2019-06-13 19:22:12,718 WARN org.apache.flink.runtime.blob.TransientBlobCache - File upload for an existing file with key t-2cef9f5c52247f757f677c1592279fb65f096544-78ffcb691eed1982c6e6833f3b5b5872 for job null. This may indicate a duplicate upload or a hash collision. Ignoring newest upload.
2019-06-13 19:26:09,505 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph - Source: Custom Source -> Flat Map (3/4) (aadeb78ac5f1019272bf7fae4c2e9836) switched from RUNNING to FAILED.
java.util.concurrent.TimeoutException: Heartbeat of TaskManager with id 86adca8a147a7fa55e4a3271d908dec1 timed out.

at org.apache.flink.runtime.jobmaster.JobMaster$TaskManagerHeartbeatListener.notifyHeartbeatTimeout(JobMaster.java:1609)
at org.apache.flink.runtime.heartbeat.HeartbeatManagerImpl$HeartbeatMonitor.run(HeartbeatManagerImpl.java:339)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.flink.runtime.concurrent.akka.ActorSystemScheduledExecutorAdapter$ScheduledFutureTask.run(ActorSystemScheduledExecutorAdapter.java:154)
at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:39)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:415)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

2019-06-13 19:26:09,509 INFO org.apache.flink.runtime.executiongraph.ExecutionGraph - Job --->>> channelStatistics start! (aecf3051a417f501df4761351e37b8c3) switched from state RUNNING to FAILING.
java.util.concurrent.TimeoutException: Heartbeat of TaskManager with id 86adca8a147a7fa55e4a3271d908dec1 timed out.

at org.apache.flink.runtime.jobmaster.JobMaster$TaskManagerHeartbeatListener.notifyHeartbeatTimeout(JobMaster.java:1609)
at org.apache.flink.runtime.heartbeat.HeartbeatManagerImpl$HeartbeatMonitor.run(HeartbeatManagerImpl.java:339)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.flink.runtime.concurrent.akka.ActorSystemScheduledExecutorAdapter$ScheduledFutureTask.run(ActorSystemScheduledExecutorAdapter.java:154)
at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:39)
at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:415)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

展开
收起
panpanpa123 2019-06-13 20:30:27 10976 0
3 条回答
写回答
取消 提交回答
  • 可能是 FGC,导致心跳超时,具体要看下日志里面是不是有连续的FGC,以及对应的时间。

    2020-03-29 22:18:02
    赞同 展开评论 打赏
  • 同问,我的也是这样,运行十几分钟就这样了

    2019-11-18 12:12:10
    赞同 展开评论 打赏
  • 老菜鸟一枚

    楼主解决了吗? 我也有这个问题

    2019-09-21 18:37:22
    赞同 展开评论 打赏
问答排行榜
最热
最新

相关电子书

更多
Flink CDC Meetup PPT - 龚中强 立即下载
Flink CDC Meetup PPT - 王赫 立即下载
Flink CDC Meetup PPT - 覃立辉 立即下载