Re: Could not resolve ResourceManager address

2022-09-21 Thread Rommel Holmes
resolve resource manager address > > > *Could not resolve ResourceManager address > akka.tcp://flink@flink-jm-svc-streaming-job:6123/user/rpc/resourcemanager_*, > retrying in 1 ms: Could not connect to rpc endpoint under address > akka.tcp://flink@flink-jm-svc-streaming-job:6123

Could not resolve ResourceManager address

2022-09-21 Thread Rommel Holmes
Hello I am trying to make a Flink application deployment in k8s, but the error message shows that the task manager can't resolve resource manager address *Could not resolve ResourceManager address akka.tcp://flink@flink-jm-svc-streaming-job:6123/user/rpc/resourcemanager_*, retrying in 100

Re: Could not resolve ResourceManager address in native kubernetes

2021-05-12 Thread Yang Wang
etAddress > /0:0:0:0:0:0:0:0%0:40399. 2021-05-10 14:09:28,894 INFO > org.apache.flink.runtime.taskexecutor.KvStateService [] - Starting > the kvState service and its components. 2021-05-10 14:09:28,979 INFO > org.apache.flink.runtime.rpc.akka.AkkaRpcService [] - Star

Re: Could not resolve ResourceManager address in native kubernetes

2021-05-11 Thread Chesnay Schepler
roviders/native_kubernetes/>) but I have an error even with the example from the documentation. The job get submitted but stays in "created" status until it timeouts after 5 minutes. In the log of the task manager, I can see that the error is "*Could not resolve ResourceManag

Could not resolve ResourceManager address in native kubernetes

2021-05-10 Thread Valentin Wallyn
status until it timeouts after 5 minutes. In the log of the task manager, I can see that the error is "*Could not resolve ResourceManager address"* What can be the issue ? Here are the logs : > ./bin/kubernetes-session.sh -Dkubernetes.cluster-id=franz-01 *

Re: Issue with Could not resolve ResourceManager address akka.tcp://flink

2020-03-27 Thread Yang Wang
is 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. Would you check whether the

Re: Issue with Could not resolve ResourceManager address akka.tcp://flink

2020-03-27 Thread Vitaliy Semochkin
, 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. Would you check whether the hostname > *prod-bigd-dn11* is reso

Re: Issue with Could not resolve ResourceManager address akka.tcp://flink

2020-03-26 Thread Zhu Zhu
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 th

Issue with Could not resolve ResourceManager address akka.tcp://flink

2020-03-26 Thread Vitaliy Semochkin
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

Could not resolve ResourceManager address on Flink 1.7.1

2019-03-12 Thread Le Xu
: Could not connect to rpc endpoint under address akka.tcp://flink@10.0.0.6:6123/user/resourcemanager.. 2019-03-12 07:39:42,884 INFO org.apache.flink.runtime.taskexecutor.TaskExecutor - Could not resolve ResourceManager address akka.tcp:// flink@10.0.0.6:6123/user/resourcemanager, retrying