尝试升级到 flink 1.3.1 时出现异常 [英] Exception when trying to upgrade to flink 1.3.1

问题描述

我尝试将集群中的 flink 版本升级到 1.3.1(以及 1.3.2)，但在任务管理器中出现以下异常:

I tried to upgrade my flink version in my cluster to 1.3.1 (and 1.3.2 as well) and I got the following exception in my task managers:

2018-02-28 12:57:27,120 ERROR org.apache.flink.streaming.runtime.tasks.StreamTask           - Error during disposal of stream operator.
org.apache.kafka.common.KafkaException: java.lang.InterruptedException
        at org.apache.kafka.clients.producer.KafkaProducer.close(KafkaProducer.java:424)
        at org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducerBase.close(FlinkKafkaProducerBase.java:317)
        at org.apache.flink.api.common.functions.util.FunctionUtils.closeFunction(FunctionUtils.java:43)
        at org.apache.flink.streaming.api.operators.AbstractUdfStreamOperator.dispose(AbstractUdfStreamOperator.java:126)
        at org.apache.flink.streaming.runtime.tasks.StreamTask.disposeAllOperators(StreamTask.java:429)
        at org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:334)
        at org.apache.flink.runtime.taskmanager.Task.run(Task.java:702)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.InterruptedException
        at java.lang.Object.wait(Native Method)
        at java.lang.Thread.join(Thread.java:1252)
        at java.lang.Thread.join(Thread.java:1326)
        at org.apache.kafka.clients.producer.KafkaProducer.close(KafkaProducer.java:422)
        ... 7 more

作业管理器显示无法与任务管理器连接.

The job manager showed that it failed to connect with the task managers.

我正在使用 FlinkKafkaProducer08.有什么想法吗?

I am using FlinkKafkaProducer08. Any ideas?

推荐答案

首先，从上面的堆栈跟踪来看:它是在操作符清理非优雅终止时抛出的(否则这段代码不会被执行).看起来好像应该紧随其后是导致最初问题的真正异常.你能提供更多的日志部分吗?

First of all, from the stack trace above: it was thrown during operator cleanup of a non-graceful termination (otherwise this code is not executed). It looks as if it should be followed by the real exception that caused the initial problem. Can you provide some more parts of the log?

如果 JobManager 无法连接到任何应该运行您的作业的 TaskManager，整个作业将被取消(并根据您的重试策略重试).您的 TaskManager 端也可能发生同样的情况.这可能是根本原因，需要进一步调查.

If the JobManager failed to connect to any TaskManager that should run your job, the whole job will be cancelled (and retried based on your retry policy). The same may happen on your TaskManager side. That may be the root cause and needs further investigation.

这篇关于尝试升级到 flink 1.3.1 时出现异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！