Nice to hear :-)
Best,
tison.
Aleksandar Mastilovic 于2019年8月23日周五 上午2:22写道：
> Thanks for all the help, people - you made me go through my code once
> again and discover that I switched argument positions for job manager and
> resource manager addresses :-)
>
> The docker ensemble now starts fi
Thanks for all the help, people - you made me go through my code once again and
discover that I switched argument positions for job manager and resource
manager addresses :-)
The docker ensemble now starts fine, I’m working on ironing out the bugs now.
I’ll participate in the survey too!
> On
Besides, would you like to participant our survey thread[1] on
user list about "How do you use high-availability services in Flink?"
It would help Flink improve its high-availability serving.
Best,
tison.
[1]
https://lists.apache.org/x/thread.html/c0cc07197e6ba30b45d7709cc9e17d8497e5e3f33de504d5
Hi Aleksandar,
base on your log:
taskmanager_1 | 2019-08-22 00:05:03,713 INFO
org.apache.flink.runtime.taskexecutor.TaskExecutor- Connecting
to ResourceManager
akka.tcp://flink@jobmanager:6123/user/jobmanager()
.
taskmanager_1 | 2019-08-22 00:05:04
Hi Aleksandar,
The resource manager address is retrieved from the HA services.
Would you check whether your customized HA services is returning the right
LeaderRetrievalService and whether the LeaderRetrievalService is really
retrieving the right leader's address?
Or is it possible that the stored
Hi all,
I’m experimenting with using my own implementation of HA services instead of
ZooKeeper that would persist JobManager information on a Kubernetes volume
instead of in ZooKeeper.
I’ve set the high-availability option in flink-conf.yaml to the FQN of my
factory class, and started the dock
