Could you also check the jobmanager logs whether the flink akka is also
bound to
and listening at the hostname "prod-bigd-dn11"? Otherwise, all the package
from
taskmanager will be discarded.
Best,
Yang
Vitaliy Semochkin 于2020年3月27日周五 下午3:35写道：
> Hello Zhu,
>
> The host can be resolved and th
Hello Zhu,
The host can be resolved and there are no filewalls in the cluster, so all
ports are opened.
Regards,
Vitaliy
On Fri, Mar 27, 2020 at 8:32 AM Zhu Zhu wrote:
> Hi Vitaliy,
>
> >> *Cannot serve slot request, no ResourceManager connected*
> This is not a problem, just that the JM need
Hi Vitaliy,
>> *Cannot serve slot request, no ResourceManager connected*
This is not a problem, just that the JM needs RM to be connected to send
slot requests.
>> *Could not resolve ResourceManager address
akka.tcp://flink@prod-bigd-dn11:43757/user/resourcemanager*
This should be the root cause.
Hi,
I'm facing an issue similar to
https://issues.apache.org/jira/browse/FLINK-14074
Job starts and then yarn logs report "*Could not resolve ResourceManager
address akka.tcp://flink*"
A fragment from yarn logs looks like this:
LazyFromSourcesSchedulingStrategy]
16:54:21,279 INFO org.apache.fli
